• 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
-[NSPersistentDocument isDocumentEdited] lazy until next click
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

-[NSPersistentDocument isDocumentEdited] lazy until next click


  • Subject: -[NSPersistentDocument isDocumentEdited] lazy until next click
  • From: Jerry Krinock <email@hidden>
  • Date: Fri, 6 Feb 2009 16:02:44 -0800

When the user updates a particular attribute of a particular object in my Core Data document-based application, the "dirty" dot in the document's window does not appear until after the user clicks again, anywhere in the window. I also find that, about 15% of the time, after subsequently clicking Save, the dirty dot will remain, again, until after the user clicks again, anywhere in the window.

Saving this tiny test document takes only milliseconds. The setter I'm using is Core Data's @dynamic, definitely KVO-compliant. Sending - processPendingChanges to the document's moc immediately after changing this attribute has no effect.

When changing the attribute, the NSManagedObjectContextObjectsDidChangeNotification is posted immediately. However, -isDocumentEdited messages sent to the document return NO until after that second click.

That's as close as I've been able to get to the root of it. Is this behavior familiar to anyone?

Thanks,

Jerry Krinock

_______________________________________________

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: Full Screen Mode With MenuBar
  • Next by Date: Re: @synchronized in thread safe accessors
  • Previous by thread: Re: @synchronized in thread safe accessors
  • Next by thread: where's my exception?
  • Index(es):
    • Date
    • Thread