On Tue, Dec 17, 2013 at 9:05 AM, Pascal Obry <pas...@obry.net> wrote: > > During a teaching session on dt a user got caught by this: > > - select a point in history (to watch the evolution) > - leave darkroom and go to lighttable > > The dev history above the last selected point is lost. > > Looks like a dangerous behavior to me. Has this been done on purpose?
The problem is that we are using history stack as an undo, which is not the intended purpose. The same happens if you are looking at a previous step of an image and you move a slider unadvertedly. > My proposal would be to remove the history only when clicking on the > [compress history stack] button. I basically would agree. Imposes more steps to discard history, but stays on the safe side. Also, I would like to have a separate undo stack, in which all changes to every slider are tracked. This is something I have discussed with Johannes before. He says that our history module would do it by just changing one define, but I still think we need some tweaking. Also I am not sure that it makes sense to store in the XMP all the processing history stack, which would happen in this case. -- José Carlos García Sogo jcs...@gmail.com ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
