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 16:18:38 -0600
- Thread-topic: KVO Bug With Keypaths
7/1/08 3:57 PM, also sprach email@hidden:
> On Tue, Jul 1, 2008 at 5:26 PM, Keary Suska <email@hidden> wrote:
>> 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?
>
> Yes, if the dictionaries are modified directly rather than using
> -setValue:forKeyPath:.
When I modify their contents, they are modified using setObject:forKey:,
which I issues KVO notifications, IIRC. At least I know it does in certain
situations, as rely on that behavior in a number of places.
I also mistyped the key path. The observed object is "relations", the path
is "order.related.content.status.value". That may make a difference.
Best,
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