7/2/08 5:42 AM, also sprach [EMAIL PROTECTED]:
>> When I modify their contents, they are modified using setObject:forKey:,
>
> -setValue:forKey: is the KVO-compliant mutator.
I tested this--also see Ken Thomases recent post. NSMutableDictionary *does*
emit KVO notifications for setObject:forKey:
On Tue, Jul 1, 2008 at 6:18 PM, Keary Suska <[EMAIL PROTECTED]> wrote:
> When I modify their contents, they are modified using setObject:forKey:,
-setValue:forKey: is the KVO-compliant mutator.
--Kyle Sludert
___
Cocoa-dev mailing list (Cocoa-dev@lists
7/1/08 5:13 PM, also sprach [EMAIL PROTECTED]:
> 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"?
"relations" (the
On Tue, Jul 1, 2008 at 11:18 PM, Keary Suska <[EMAIL PROTECTED]> 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 m
7/1/08 3:57 PM, also sprach [EMAIL PROTECTED]:
> On Tue, Jul 1, 2008 at 5:26 PM, Keary Suska <[EMAIL PROTECTED]> 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 obje
On Tue, Jul 1, 2008 at 5:26 PM, Keary Suska <[EMAIL PROTECTED]> 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
7/1/08 3:01 PM, also sprach [EMAIL PROTECTED]:
> On Tue, Jul 1, 2008 at 9:50 PM, Keary Suska <[EMAIL PROTECTED]> 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 situa
On Tue, Jul 1, 2008 at 9:50 PM, Keary Suska <[EMAIL PROTECTED]> 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.relat
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
