I am writing a program which has a two-column table. The user can
fill in the table with whatever he or she wishes, but sometimes it is
possible to determine what should be displayed in the left column by
looking at what is displayed in the right column. I have set up the
program so that
IMHO, if the user performed a single action to get to the current
state, then it shouldn't take more than one undo to get to the
previous state. So, as a user, I'd prefer #2.
On Fri, Apr 17, 2009 at 9:26 AM, K.Darcy Otto do...@csusb.edu wrote:
I am writing a program which has a two-column table.
Yes, I was thinking this too, at first. But then I started to look
around to see if I could find analogous situations. The closest I can
come is when Pages has a table - let's say 2x2. When the user is in
the bottom right cell, and presses tab, two things happen
simultaneously: the data
I would not use Pages as a model for undo. There are quite a few areas
where its undo are horrific and wrong and have caused me to lose data.
On Apr 17, 2009, at 11:48 AM, K.Darcy Otto wrote:
Yes, I was thinking this too, at first. But then I started to look
around to see if I could find
The problem with the 2 undo approach is when you start to think about
redo.
What append if you undo twice and redo once.
- You restore only one value, and get a state that should not be
possible as the inference function would have complete the last row if
it was done by the user.
- You
