Re: Strategy for acting on changes in child objects?
Re: Strategy for acting on changes in child objects?
- Subject: Re: Strategy for acting on changes in child objects?
- From: Graham Cox <email@hidden>
- Date: Thu, 7 May 2009 16:32:32 +1000
On 07/05/2009, at 4:18 PM, Seth Willits wrote:
It's still a little "clunky" (on the child-side) but less-so than
other ideas I had, and feels more proper than the ones I've been
using.
Yep, it's a little clunky ;-) (If anyone has a better solution I'm all
ears). It would be nice if there were an API that returned a list of
all of an object's properties as discoverable by the normal
valueForKey: rules, though I'm not sure it's technically possible.
It's also all-or-nothing, though of course the observer can simply
ignore any properties it's not interested in when it receives the
notification.
--Graham
_______________________________________________
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