-[NSUserDefaultsController save:]
-[NSUserDefaultsController save:]
- Subject: -[NSUserDefaultsController save:]
- From: Brent Gulanowski <email@hidden>
- Date: Thu, 14 Oct 2004 23:41:42 -0400
- Domainkeys-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=edfaaKnhvw4L0tMsR1NxN/seR8CfTRZw0T4Pi37cC66qCHQ/BKv6Xp/RaKe9T5g8kndKnVRMd+/pEhsGSNlWXxPkEpmwtE0NXf8718FNpc572do9FfsHSlOwfxMhIj7qpqH2YdtISR6Bpl4toGKJ2yPFx0IR6oqEJ0X2JXOF7gE
I looked around for some extra info on this and had no luck so I'll
beg forgiveness if I missed it.
If I create a register a dictionary of defaults to NSUserDefaults the
old way, set NSUserDefaultsController appliesImmediately to "NO" and
then use -save:, all the defaults in the registration domain get saved
to my preferences plist, thereby making what was meant to be volatile
now persistent. Is that supposed to happen? Seems like it shouldn't,
since many of those defaults were not set by the user and should not
outlast a run session, especially, as in my case, if the registration
defaults can change with the environment, or, even more importantly,
if they cannot be changed by the user at all!
Maybe it's just me, but it's a pain.
--
Brent Gulanowski
http://www.boredastronaut.com
_______________________________________________
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