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 protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
