Il 29/11/2012 09:40, Štěpán Roučka ha scritto: > On Thu, Nov 29, 2012 at 5:14 AM, johannes hanika<[email protected]> wrote: >> >> On Thu, Nov 29, 2012 at 12:59 PM, francis<[email protected]> wrote: >>> On 12-11-28 01:40 PM, George Pop wrote: >>> >>> I didn't mean branching in any way, just a linear undo/redo. The history >>> stack as it exists right now is limited in one significant way. >>> >>> For example, if you adjust the tone curve, now the tone curve is at the top >>> of the stack, and you can certainly go back to the previous state. But let's >>> say you make one further adjustment to the tone curve, and you don't like >>> it, and you want to go to the previous state _of the tone curve_. You can't, >>> because the history stack only has one entry for the module at the top, and >>> will create a new entry only when you switch to a different module. This is >>> problematic especially with the curve-based modules, because you can't >>> easily restore the previous curve. >> > I agree with this, although I somehow learned to work without this > fine-grained history > stack. > >> the hard part is to tell what's the previous one while you're >> continuously dragging a curve point. you need some mechanism to avoid >> spamming your history stack with one million entries per second. >> introducing a new item after a certain timeout sounds like a terrible >> plan. > Perhaps making a new history entry only after you release mouse drag in > the curve editor would be a good starting point? And perhaps all such history > entries could be deleted once you switch to some other module? > Just some ideas, I am not sure how this woul work IRL... > > Stepan
I agree with johannes. Is not a good idea to populate history stack of a lot of records. It will become soon difficult to use. I'm not sure the undo features should match the current history stack feature. I mean: I see history stack as a log of macro-operation of applied plugins. It is useful to see if a plugin produce a better result and permits to return to a previous version. I see the undo feature as something different. The undo could be an hide stack and the user could navigate it using shortcuts (ctrl-z/ctrl-y?). After I'm satisfied of the current result I could fix it to the history stack, and create a new macro-step of my workflow. In this case, a "save step" button is imo a useful solution. I admit software like gimp has an undo history, and maybe it could be like to navigate, but I found more useful a "macro history stack". just my2cents Ivan ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: VERIFY Test and improve your parallel project with help from experts and peers. http://goparallel.sourceforge.net _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
