> Yes. The app that writes the pref should call synchronize and send its
> signal, then the app that reads calls synchronize when it receives it. I have
> a pair of apps that do that; I use NSDistributedNotificationCenter and the CF
> equivalent CFNotificationCenterGetDistributedCenter for the signals.
That sounds quite elegant, thanks!
--
shamyl zakariya
- so much for pathos
On Jul 14, 2010, at 3:03 PM, Lee Ann Rucker wrote:
>
> On Jul 14, 2010, at 9:20 AM, Greg Guerin wrote:
>
>> Shamyl Zakariya wrote:
>>
>>
>>> If not, what's the best practice here? And if I were to use some
>>> sort of apple event fired from the prefpane or some other technique
>>> to let the app know its defaults have changed, how do I get the
>>> user defaults controller in the headless app to apply the updates?
>>
>>
>> If I understand the question correctly, then when the signal is
>> received, your headless app calls -synchronize on the
>> NSUserDefaults. This assumes you don't have any shared-access
>> contention issues.
>
> Yes. The app that writes the pref should call synchronize and send its
> signal, then the app that reads calls synchronize when it receives it. I have
> a pair of apps that do that; I use NSDistributedNotificationCenter and the CF
> equivalent CFNotificationCenterGetDistributedCenter for the signals.
> _______________________________________________
>
> 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/shamyl%40gmail.com
>
> This email sent to [email protected]
_______________________________________________
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]
