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.
Right now, we can work around this limitation by doing a fake/dummy operation
(like toggling a random module) to make sure that a new entry will be created
in the history before a new adjustment, but this is less than ideal.
Am I making sense?
George
> Date: Thu, 29 Nov 2012 09:44:07 +1300
> Subject: Re: [Darktable-users] "OK" button
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
>
> On Wed, Nov 28, 2012 at 11:10 PM, George Pop <[email protected]> wrote:
> > Actually, I don't think the OK button is the solution. I like how changes
> > are applied live, I just would like to have undo.
>
> the history stack is precisely an undo list. it's just not a tree, so
> if you go back and re-apply new stuff, you lose the old branch.
>
> > The two aren't
> > incompatible with one another. A text editor, for example, applies the
> > changes live, and every keystroke adds a step to the undo history.
> >
> > George
> >
> >
> > ________________________________
> > Date: Wed, 28 Nov 2012 09:26:23 +0100
> > From: [email protected]
> > To: [email protected]
> > Subject: [Darktable-users] "OK" button
> >
> >
> > I agree with you, Ivan. I also use a fake operation to create the proper
> > steps in the history (usually, I just toggle the over/underexposed
> > indicator). I don't know what would be the ideal solution. This problem is a
> > consequence of the fact that changes are applied live, without an "OK"
> > button. It would be nice to have real undo, especially with the modules that
> > don't take numerical inputs (Tone curve, Color zones etc.). It's almost
> > impossible to restore a curve perfectly, and that discourages
> > experimentation.
> > George
> >
> >
> > + 1
> >
> > Philippe DELETREE
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel
> > hardware, programming and related areas? Interviews and blogs by thought
> > leaders keep you ahead of the curve. http://goparallel.sourceforge.net
> > _______________________________________________ Darktable-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/darktable-users
> >
> > ------------------------------------------------------------------------------
> > Keep yourself connected to Go Parallel:
> > INSIGHTS What's next for parallel hardware, programming and related areas?
> > Interviews and blogs by thought leaders keep you ahead of the curve.
> > http://goparallel.sourceforge.net
> > _______________________________________________
> > Darktable-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/darktable-users
> >
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
