• 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: Recomputing non-standard Core Data attributes when child MOC is saved?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Recomputing non-standard Core Data attributes when child MOC is saved?


  • Subject: Re: Recomputing non-standard Core Data attributes when child MOC is saved?
  • From: Mike Abdullah <email@hidden>
  • Date: Tue, 23 Jul 2013 22:57:17 +0100

On 19 Jun 2013, at 15:45, Noah Desch <email@hidden> wrote:

> I have had really weird issues with NSManagedObjects KVOing themselves. I would recommend you instead override the dynamic setters for all the attributes whose value affects your computed property and clear your pre computed value there.

There is an important difference to note between the two:

During undo/redo operations, Core Data does not call custom setter methods you may have implemented. Instead it sets the primitive value more directly. KVO by contrast still fires during undo/redo.


_______________________________________________

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


  • Prev by Date: Re: Good behavior with full-screen and NSStatusWindowLevel windows
  • Next by Date: Re: view based NSTable View - button not firing
  • Previous by thread: Re: view based NSTable View - button not firing
  • Next by thread: WebView & Silverlight
  • Index(es):
    • Date
    • Thread