Combining the history and snapshots would be interesting. How about placing a "S" marker at one end of the History entry as a separate entity when a snapshot is taken,Then just clicking on the marker would display the snapshot that is appropriate.
I also have had history losses (generally through my inattention)! Yes, better security on the history would be great. David On 13-12-17 03:14 AM, Per Östlund wrote: > It would also be nice to somehow couple the history to the snapshot > feature. As it is I find the snapshot feature somewhat useless, since > you have to remember yourself what the difference between the snapshots > are. I think that has been mentioned before on this list. I'm not sure > what the best way to handle that would be, maybe add a button that > replaces the current history with the snapshot's history. > > /Per Östlund > > On 2013-12-17 12:09, Jose Carlos Garcia Sogo wrote: >> 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. >> > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
