Re: Forcing a refresh on a bound control
Re: Forcing a refresh on a bound control
- Subject: Re: Forcing a refresh on a bound control
- From: "Hamish Allan" <email@hidden>
- Date: Tue, 20 May 2008 20:12:31 +0100
On Tue, May 20, 2008 at 12:43 AM, Christiaan Hofman <email@hidden> wrote:
> The problem is that at some point the dependent key depends on a key for
> /another/;object. And this can not give automatic KVO notifications for the
> dependent key (using Tiger API), unless you actually use a KVC compliant
> setter for the dependent property.
Ah, yes, sorry, I didn't read the thread back far enough. And I should
have known better, seeing as I asked about this myself in 2005:
http://www.cocoabuilder.com/archive/message/cocoa/2005/12/23/153070
I got the highly useful answer "that's just how it works". So I asked
again earlier this year:
http://www.cocoabuilder.com/archive/message/cocoa/2008/4/17/204429
The particular reason for my re-asking was that I had discovered that
NSArrayController doesn't bother to populate its before/after values
properly. Given this glaring bug, and Keary's pertinent question: "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?", although I hesitate to recommend it, I
just can't believe that the will/did hack will break anything, despite
mmalc's protestations.
Hamish
_______________________________________________
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