• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Triggering a Method when a Core Data Property changes.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Triggering a Method when a Core Data Property changes.


  • Subject: Re: Triggering a Method when a Core Data Property changes.
  • From: Kyle Sluder <email@hidden>
  • Date: Sat, 17 Oct 2009 11:37:42 -0700

On Sat, Oct 17, 2009 at 8:34 AM, Jerry Krinock <email@hidden> wrote:
> Now, I'm not sure if you should do that, or observing the tree controller as
> recommended by Kyle.  However, since I don't have a tree controller in a
> project of mine, I've kind of done what you suggested.

It depends on what you're trying to do.  Both are logical places to
put different kinds of observations.

> http://mikeash.com/?page=pyblog/key-value-observing-done-right.html

We've solved the problem differently from Mike Ash.  See OFBinding in
the OmniFoundation framework.  As far as I can tell, Apple has done
the same thing with NSTableBinder and family.

--Kyle Sluder
_______________________________________________

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

References: 
 >Re: Triggering a Method when a Core Data Property changes. (From: Joshua Garnham <email@hidden>)
 >Re: Triggering a Method when a Core Data Property changes. (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Subclassing a view class from an external framework
  • Next by Date: Re: Subclassing a view class from an external framework
  • Previous by thread: Re: Triggering a Method when a Core Data Property changes.
  • Next by thread: GC and atomic getters/setters
  • Index(es):
    • Date
    • Thread