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: Fri, 8 May 2009 10:31:37 +1000
On 08/05/2009, at 1:40 AM, Shawn Erickson wrote:
On Thu, May 7, 2009 at 1:46 AM, Graham Cox <email@hidden>
wrote:
I suspected it might be but frankly I found the documentation
confusing and
couldn't get it to work. Also, it's 10.5 only, though there is a
deprecated
older method that serves a similar purpose.
The older method and the new method work just fine, I use it heavily
for situations of dependent properties in a project that supports 10.4
and later.
-Shawn
Oh I'm sure it works ;-)
The problem I have with it is that I can't precisely tell from the
documentation what problem it solves, and whether it is the same
problem that I've had in the past (and Seth has now) which I solved as
outlined. It seems to solve a closely related but slightly different
problem, but I'm not sure. My inability to get it to work reflects my
lack of a complete understanding of what it does.
Maybe you could point me to some supplementary documentation (external
to Apple's if necessary) that explains it in a bit more detail?
--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