Closed GoogleCodeExporter closed 9 years ago
Yep, I didn't complete this part. This is not even linked to Undo: After an
X-swap,
swap to spare and back, or change the active layer (2 things that don't modify
the
image's history), and you'll the remap is already forgotten.
(internal notes: X-Swap doesn't remap the layers, only the visible buffer. Need
to
test all palette operations when this is done, because the history may not be
handled
well anyway. Normal behavior should be as follows : First backup saves 'no
layers'
because normally only the palette is going to be changed. If there's any remap
(and
only the first time), it should first do a full backup - and even *replace* the
original, so it will appear as a single atomic Undo/Redo step. Also, on Cancel,
the
current backup should be rolled back so it's not in the Undo/Redo chain.)
Original comment by yrizoud
on 2 Dec 2009 at 1:09
Original comment by pulkoma...@gmail.com
on 15 Jan 2010 at 7:39
Should be fixed in r1271.
Original comment by pulkoma...@gmail.com
on 17 Jan 2010 at 8:37
Original issue reported on code.google.com by
cameron...@comcast.net
on 27 Nov 2009 at 4:17