Am 09.11.2014, 14:13 Uhr, schrieb Patrick Shanahan <[email protected]>:
> > Therein lies mis-understanding or mis-communication :^( > > I do not want to wander thru history and make changes but *only* the > *last* change, as: if I add brightness, to return to the previous > brightness level and not to the *default* brightness level, or making > blacklevel changes or midlevel or .... > So, you don't want to revert the very last change in a module, you would like to have the state of module before editing. If you duplicate the module with the same settings before you edit again, isn't that what you want? >> There could be a technically simple solution that is very similar to >> what actually happens in the undo of many programs: create an item in >> history stack whenever anything is changed in any module. >> Trouble is: recording every little change will bloat the stack a lot, >> making it irrelevant. > > Only maintain the changes for the *current* module and compress them upon > leaving that module Here you mean something like a temporary history stack for each module? ------------------------------------------------------------------------------ _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
