ANN: GLX2 3.0.10

[Mark Wieder]

Alejandro-

Saturday, August 4, 2012, 1:55:49 PM, you wrote:

> I agree that "allowing undos past the last save is a huge advantage."

Well, this is turning out to be a more interesting conversation than I
expected. At first I thought that unlimited undos was the holy grail
of an undo mechanism. Then it appeared that there were complications
with allowing undos past the last save - you do want to know where the
last save point is so that you don't accidentally undo code that's
already working and saved. So there are nuances to this that I hadn't
originally thought through.

My current thinking is to allow undos to the last save point without
any additional trappings (obviously I have this already). A save of
the current stack will place a "save" marker in the array, similar to
the "count" marker that acts as an array index. If the count marker is
greater than the save marker (the user has backtracked to a point
before the last save) then either bring up a warning confirmation
dialog or require a different set of keypresses... although I'm at a
loss to decide what keys these should be... command-Z is undo,
command-shift-Z is redo, command-option is already taken... I think I
like the annoying confirmation dialog since it does do the disruptive
step of making you think about what you're about to do, and I don't
think the situation should come up all that often.

-- 
-Mark Wieder
 mwieder at ahsoftware.net