• 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: Undo and Core Data issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Undo and Core Data issue


  • Subject: Re: Undo and Core Data issue
  • From: Ben Trumbull <email@hidden>
  • Date: Wed, 5 Mar 2008 18:31:13 -0800

I call processPendingChanges from both the *Will* and *Did* notifications.

Please stop. It doesn't make sense for the context to coalesce pending changes in the middle of the change to a single object during the KVO callbacks.


Your original problem description is a bit sparse. Common problems that produce that symptom are people doing things in a managed object's initializer they shouldn't, people doing things in -awakeFromInsert/Fetch they shouldn't, or the undo stack having more entries on it than they expect (i.e. undo works just fine, but the stack isn't coalesced as the user expects)
--


-Ben
_______________________________________________

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


  • Follow-Ups:
    • Re: Undo and Core Data issue
      • From: Michael Latta <email@hidden>
  • Prev by Date: Re: Core Data, SQLite, and Housekeeping
  • Next by Date: Re: NSTextField keyboard event
  • Previous by thread: Re: Undo and Core Data issue
  • Next by thread: Re: Undo and Core Data issue
  • Index(es):
    • Date
    • Thread