Re: How does bind:toObject:withKeyPath:options: work?
Re: How does bind:toObject:withKeyPath:options: work?
- Subject: Re: How does bind:toObject:withKeyPath:options: work?
- From: Keary Suska <email@hidden>
- Date: Thu, 17 Apr 2008 09:32:15 -0600
- Thread-topic: How does bind:toObject:withKeyPath:options: work?
on 4/17/08 4:50 AM, email@hidden purportedly said:
>> I think you can use of a class that inherits from NSArrayController
>
> Thanks for your reply. Subclassing and caching did occur to me (which
> I should have mentioned), but having to do that sort of thing rather
> defeats the purpose of automatic KVO (it would be simpler just to
> override setArrangedObjects:), so I'm still interested in why bindings
> are designed this way (I almost titled the thread "Bindings -- broken
> by design?" but I thought that would be a bit inflammatory :] ).
Although I have come across a situation where what you suggest would be
useful, it is rare. Although, I believe that Core Data makes extensive use
of this to manage faults. Anyway, it may seem immediate in your situation,
but this is really because of a class that does *not* use bindings
correctly, as you are aware. Rather, perhaps your question should be, why
are NSController and its subclasses (because this problem, IIRC, effects all
NSController classes) broken by design, and not fixed even after two full OS
releases?
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:
This email sent to email@hidden