Chris's Wiki :: blog/programming/UndoNotEnough Commentshttps://utcc.utoronto.ca/~cks/space/blog/programming/UndoNotEnough?atomcommentsDWiki2009-08-13T19:21:22ZRecent comments in Chris's Wiki :: blog/programming/UndoNotEnough.By Chris Siebenmann on /blog/programming/UndoNotEnoughtag:CSpace:blog/programming/UndoNotEnough:7cfded5d4dda367e78eebdc803b94dee221ca7f4Chris Siebenmann<div class="wikitext"><p>In this situation, I think that trying to work out which modifications
the user considers dependent on each other is either hopeless or at least
a very hard task that the program shouldn't be trying to do. The usual
approach is just to have on/off toggles and leave it up to the user to
adjust modifications that they consider dependent.</p>
<p>(Some programs have the idea of 'layers', where you can group a set of
modifications together and then turn them on and off together. The one
I know of has this fall out as part of restricting the modifications to
only part of the image.)</p>
</div>2009-08-13T19:21:22ZFrom 71.250.234.178 on /blog/programming/UndoNotEnoughtag:CSpace:blog/programming/UndoNotEnough:534e17d5b8556f6e71cee413c1af6c118dffbeb5From 71.250.234.178<div class="wikitext"><p>Ideally, the program would classify each subsequent edit, and classify each as being dependent on each of the previous steps, so that you could roll back non-systemic changes. What if you edited a photo and lightened a face, then later decided that your initial exposure was off, so you go back to correct that. Should the program know your motivation for lightening the face? Should it roll that back, too, or should it leave it, and give you an overly bright face?</p>
<p>It's definitely complex decision making.</p>
<p>Matt Simmons<br>
<a href="http://www.standalone-sysadmin.com/blog">http://www.standalone-sysadmin.com/blog</a></p>
</div>2009-08-13T14:33:58Z