Re: insertObject:in<Key>AtIndex: not being called.
Re: insertObject:in<Key>AtIndex: not being called.
- Subject: Re: insertObject:in<Key>AtIndex: not being called.
- From: mmalcolm crawford <email@hidden>
- Date: Sun, 3 Apr 2005 01:51:15 -0800
On Apr 3, 2005, at 1:31 AM, Paul Szego wrote:
Ok - so the bottom line seems to be: if you're wanting KVC write
access, you have to know whether you're dealing with a to-many
property. In that case, use mutableArrayValueForKeyPath: instead of
just setValue:forKey: to cater for the situation where indexed
accessors are provided.
Correct.
Which leads to me next question about bindings, which I've posted
elsewhere. If I bind a to-many property that's providing indexed
accessors, the default bind: behaviour provided in NSObject tries
to call setValue:forKey: instead of using
mutableArrayValueForKeyPath:, and so I get a "not KVC compliant"
error message. Is this what should happen?
No -- assuming you're using an array controller?
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden