Response/comment below.
Mimi Yin wrote:
The only disadvantage of Yes/No dialog buttons is that if the buttons
themselves are descriptive, than users don't need to read the dialog
text. So as a rule, I've been trying to avoid Yes/Not buttons in
dialogs on the Desktop. (Although admittedly, the message you have is
pretty short.)
I actually tried in my e-mail yesterday to write a sensible
prompt/button combination that used Yes/No instead of action words,
because I was initially thinking it might actually be less confusing.
But I couldn't come up with wording that made it clear what would happen
when clicking each of the buttons.
And now, thinking on it further -- it seems like there are really three
options:
1. Save the changes to the server.
2. Ignore the changes and change the contents of the form to the new
selection.
3. Cancel the action and return back to the form to verify what the
changes are before deciding whether or not to save.
May be overkill -- but users may not be totally sure *what* changes they
made, and want to double-check the form before keeping the changes or
throwing them out.
I hate it when the UI forces me to make destructive changes (e.g. save
or throw out my changes) if I'm not totally sure what I've done.
Thoughts?
Matthew
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
