Re: KVO Bug With Keypaths
Re: KVO Bug With Keypaths
- Subject: Re: KVO Bug With Keypaths
- From: Keary Suska <email@hidden>
- Date: Tue, 01 Jul 2008 15:26:22 -0600
- Thread-topic: KVO Bug With Keypaths
7/1/08 3:01 PM, also sprach email@hidden:
> On Tue, Jul 1, 2008 at 9:50 PM, Keary Suska <email@hidden> wrote:
>
>> I thought I saw somewhere a bug in KVO where notifications aren't properly
>> sent in certain situations when "upper" parts of the path are updated. E.g.,
>> I have a situation where is am observing a keypath
>> "relations.related.content.status.value" but notifications aren't sent when
>> "related" is changed (in a KVO-compliant way).
>
> Is every part of the key path KVO compliant? If not, the whole chain is
> broken.
I think so. "relations" and "content" are read-only (no public setters).
Notifications aren't sent for them as they are never changed throughout the
lifecycle of an object. I.e., they are both dictionaries, and only their
contents, not the properties themselves, may vary. Would this be an issue?
> Is any part of the key path a descendant of NSObjectController? If so,
> the whole chain may be broken ;)
Nope.
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