On 29 November 2012 04:14, 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. > > 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.
That's why the OK button is proposed, AFAIU. It would take extra step, hit OK, but there is clear advantage for those who prefer finer control over the history steps. Perhaps, the OK button could be configurable to enable automatic on-fly application of settings, for those who prefer the old behaviour. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ 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
