Tom Rathborne ([EMAIL PROTECTED]) wrote:
> On Wed, Jun 07, 2000 at 04:25:49PM +0200, Sven Neumann wrote:
> > I still believe that it is a bad idea to waste undo steps for
> > operations that don't save any shadow tiles.
> 
> I agree. If I'm on a machine with limited resources and have the GIMP
> set up for only, say, 8 levels of undo, I don't want to lose the
> ability to undo image changes just because I toggle a few layers on
> and off.

Agreed... :-)

> The undo history dialog should probably note which actions count as
> "undo levels" and which don't. Also, it would be nice to be able to
> force a tile-changing undo (e.g. with Ctrl-Shift-Z) ... if you do 30
> layer moves/visbility changes then you probably don't want to have to
> hit Ctrl-Z 30 times just to undo your last pixel change.

This comes very close to the idea of micro- vs. macro undo's we discussed
at the gimpcon. Ctrl-Z could undo the last micro-operation:
Toggling visibility, undo the last stroke... and ctrl-shift-z
could undo all operations of the same type: Lets say we have
the following operations on the stack:

Stroke with Brush
Stroke with Brush
Bright/contrast
Bright/contrast
Bright/contrast
Bright/contrast
Bright/contrast
Stroke with Brush
Stroke with Eraser
Stroke with Eraser
Stroke with Eraser

Ctrl-Z would work as usual, Shift-Ctrl-Z would undo the last three steps
(all erasing) then the single brush-stroke (like ctrl-Z) and then all
contrast-changes....

However, this is probably not possible for 1.2. I have no real clue
of the undo system, but it may be possible that Brush and Eraser are
currently undistinguishable for the Undo-system. To hack around this
we could set some kind of flag to the current undo-step when the
tool changes or the operation is fundamentally different from the
previous. Ctrl-Shift-Z would then jump to the next undo-step with this
flag set...

Just my 0.02 DM.

Bye,
        Simon

-- 
      [EMAIL PROTECTED]       http://www.home.unix-ag.org/simon/

Reply via email to