Correct in practice, although the principle is more that preferences
shouldn't be that onerous to change back to how they were. The lack of
needing to click "Apply" helps here too: since each change is
reflected instantly, if something goes horribly wrong, the user knows
EXACTLY what made it go horribly wrong. Feel free to implement the
Windows way (just keep an NSMutableDictionary in your app delegate
that updates whenever the preferences window is opened, and syncs back
to the user defaults when cancel is clicked) if your preferences are
extensive enough or changes to them destructive enough that you need it.
-Daniel
On Jul 31, 2009, at 9:54 AM, Alexander Bokovikov wrote:
Hi, All,
Hope this is not an offtopic here...
I'm quite new in Mac world, and one of essential differences from
Windows, which I've noticed, is how Preferences changes are applied.
Unlike to usual Windows GUI, preferences are applied instantly on
Mac, i.e. just as user changes a value. There is no "Cancel" button
resetting values to the state, which they had at the moment, when
Preferences panel was opened. Though there is "Restore Defaults"
button, but it does just what it says - it restores so called
"factory defaults", which are not the same, as previously saved
values.
I'm reading "Cocoa Programming" by Aaron Hillegass, now, and he
describes just the same Preferences functionality, as above.
Am I missing something? Or is this the general user interface
building strategy for Cocoa applications or for Mac OS? Is it
assumed that user will never wish to return to previously saved
values?
Thanks.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
