I guess Cocoa just likes me more. :-)
Thanks for the answers.
--
Seth Willits
On Mar 18, 2013, at 7:44 AM, Uli Kusterer wrote:
> Odd, my experience has been exactly the opposite. Unless I bind to
> NSUserDefaultsController, I don't get notified when other parts of my app
> change a default
Odd, my experience has been exactly the opposite. Unless I bind to
NSUserDefaultsController, I don't get notified when other parts of my app
change a default. So I guess the answer is: "It always breaks on Uli's work
Mac" :-)
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere...
On Mar 17, 2013, at 6:00 PM, Seth Willits wrote:
> On Mar 17, 2013, at 11:31 AM, Ken Thomases wrote:
>
>>> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
>>> there any point in using NSUserDefaultsController when binding to a default
>>> through code? (Or using KVO,
On Mar 17, 2013, at 11:31 AM, Ken Thomases wrote:
>> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
>> there any point in using NSUserDefaultsController when binding to a default
>> through code? (Or using KVO, also.) It's always seemed to work monitoring
>> NSUserDe
On Mar 17, 2013, at 1:06 PM, Seth Willits wrote:
> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
> there any point in using NSUserDefaultsController when binding to a default
> through code? (Or using KVO, also.) It's always seemed to work monitoring
> NSUserDefault
In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
there any point in using NSUserDefaultsController when binding to a default
through code? (Or using KVO, also.) It's always seemed to work monitoring
NSUserDefaults directly.
--
Seth Willits
___
