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: Seth Willits <email@hidden>
- Date: Thu, 7 May 2009 13:41:16 -0700
On May 7, 2009, at 12:25 PM, Seth Willits wrote:
Graham's idea notifies the parent of any change in the child without
having to use an "isModified" key, which is a bit cleaner. I think
an even better solution would be to merge Mike Ash's dedicated KV
observer object with the general idea of Graham's. I'm going to have
to fiddle a bit.
Here's a (incomplete) example of what I was thinking:
http://www.sethwillits.com/temp/PCKVOTest.zip
I like it because:
1) Simple interface for the parent to use
2) Simple method for the child to implement
3) Parent has a unique selector being called
4) No hacky setValue:forKey: overrides required
It feels like a good direction to head in.
--
Seth Willits
_______________________________________________
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