Re: Preferences UI operation theory
Re: Preferences UI operation theory
- Subject: Re: Preferences UI operation theory
- From: John Timmer <email@hidden>
- Date: Wed, 05 Jan 2005 10:42:49 -0500
> That got me thinking:
> Are there any rules of thumb as to when a preference change happens
> immediately and when it applies later (such as next open document)?
> Somewhat of a reverse way of asking this: Is there any standard for
> when to apply a preference to the active document vs to the next opened
> document?
>
> I just wasn't sure if there were any "standards" that I missed finding
> in the documentation. II lean towards letting the user edit the
> "defaults", and the active document.
Just an added thought on why many preferences changes (or similar dialogs)
should result in immediate response:
One of the interface abominations that frustrates me to no end is a dialog
where you could set a ton of options, but not have them take effect until an
"apply" button is pressed. Typically, I'd wind up changing a bunch of
options, hitting apply, and finding that the results were something unusable
(ie - change font, size, add bold, etc. and then hit apply only to find your
text running off the end of a diagram). Undo would roll back all the
changes, and then I'd have to apply each individually to see where the
problem came in.
Having live updates lets me evaluate the effects of each change
incrementally, and hopefully provides for an undo as soon as a given change
causes problems. It makes for much better interface.
Cheers,
JT
_______________________________________________
This mind intentionally left blank
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden