Thread-topic: Problem with NSUserDefaultsController
User-agent: Microsoft-Entourage/12.12.0.080729
8/31/08 10:13 AM, also sprach email@hidden:
> I've been playing around with bindings to NSUserDefaultsController in
> a very simple app to test saving preferences, but the
> [sharedUserDefaultsController save:self] method seems to return
> immediately without waiting for the save operation to complete.
>
> The save does actually take place, which I can see if I open the
> plist file in Property List Editor, but if the very next line after
> sending the save message is one which reads a property from the
> plist, it's the old value which gets returned rather than the newly
> saved one.
The -save: method is unintuitive in name. It does not, as you may think,
save changes to disk. It simply commits any changes to the NSUserDefaults
object. It's a no-op if appliesImmediately is YES. The only way to force a
save is to call -synchronize on NSUserDefaults.
Best,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
