Re: KVO Bug With Keypaths
Re: KVO Bug With Keypaths
- Subject: Re: KVO Bug With Keypaths
- From: "Hamish Allan" <email@hidden>
- Date: Wed, 2 Jul 2008 00:13:52 +0100
On Tue, Jul 1, 2008 at 11:18 PM, Keary Suska <email@hidden> wrote:
> 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.
So to clarify: "related" is a dictionary that always contains a key
called "content", the object for which is a dictionary that always
contains a key called "status", the object for which is always
KVO-compliant for "value"?
And you can getValueForKey:@"order.related.content.status.value"
directly, but when you set the object for either of those keys, you
fail to get notified?
What happens if you register for notifications for
@"order.related.content.status", @"order.related.content", etc.? Do
you get any of those notifications?
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