• 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
NSManagedObject: Best place to start observing SELF
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSManagedObject: Best place to start observing SELF


  • Subject: NSManagedObject: Best place to start observing SELF
  • From: email@hidden
  • Date: Sun, 7 May 2006 15:19:08 -0700

I've read the documentation for NSManagedObject, and its discouraged to initialize attributes there, which is understandable, but is it OK if one adds self to be observed via addObserver:forKey from the NSManagedObject init? Or is there a reason in this case to do it only in awakeFromFetch/awakeFromInsert? Basically my object wants to watch itself for its entire life, until its dealloced, should I just observe starting in awakeFromFetch/awakeFromInsert and un-observe from didTurnIntoFault ? In the scope of coredata then waiting until dealloc is unnecessary?

I think this is probably best, but am curious for other's insight.

Thanks.

Andre
email@hidden



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: object type testing
  • Next by Date: Howto access model element from NSTableView selection ?
  • Previous by thread: Re: filling NSImage with binary data from NSData
  • Next by thread: Howto access model element from NSTableView selection ?
  • Index(es):
    • Date
    • Thread