Re: Undo (UI Concept)
Re: Undo (UI Concept)
- Subject: Re: Undo (UI Concept)
- From: Clark Cox <email@hidden>
- Date: Fri, 17 Apr 2009 09:33:19 -0700
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 <email@hidden> wrote:
> 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 a user can
> turn on an "inference" function, so if the user has:
>
> Column 1: Blank
> Column 2: X
>
> Then the program will automatically fill in "A" for column 1 (because there
> is no other possibility, given the "X" in column 2). So the table now looks
> like this:
>
> Column 1: A
> Column 2: X
>
> Now, the question is, how to implement undo. There are at least two
> possibilities:
>
> (1) Undo returns column 2 to its previous state, before "X" was entered. An
> additional undo is required to revert column 1 to blank.
> (2) Undo returns column 2 to its previous state, and column 1 to blank.
>
> I'm not sure what is best, from the perspective of designing a UI. I have
> currently implemented (2), but I have a sneaking suspicion (1) might be more
> appropriate. Note that the "A" in column 1 is inferred, but there is
> nothing wrong or odd with it standing alone.
--
Clark S. Cox III
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden