On 12/11/2010, at 3:30 AM, Ken Thomases wrote: > You should not override -setValue:forKey: or -valueForKey: if you can avoid > it. Instead, implement the methods -setValue:forUndefinedKey: and > -valueForUndefinedKey:. They are precisely for implementing "dynamic" > properties in this manner.
Understood, but the OP's problem as I understand it is that it's not that the key is undefined, but the value associated with it is uninitialized. So rather than return nil, or zero, he wants to trigger a remote fetch of the value. KVC doesn't appear to provide a mechanism for that out of the box. --Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
