On Feb 13, 2009, at 9:36 PM, I. Savant wrote:
On Feb 13, 2009, at 5:34 PM, Ken Thomases wrote:
Contrary to I. Savant, I don't think going through NSUserDefaults
or CFPreferences will work. It still won't inform the necessary
processes of the change in an active manner.
You're likely right - the process in question would have to be
listening for changes to its preferences, which it's probably not.
I don't even think there's a supported way for it to listen for
changes. CFPreferences and NSUserDefaults can synchronize with
externally-made changes, but in order to detect changes you'd have to
make a record of the pre-synchronize prefs, synchronize, and then
compare the new state to the old. Maybe NSUserDefaultsController does
this -- I don't know, but I doubt it.
However, my point was to illustrate that merely changing a plist is
the absolute least likely to trigger the desired change in the
active application / system process using that plist as a persistent
store for the state of its preferences. [...]
Sure. Agreed.
Cheers,
Ken
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
