Hi, some code may help! When using its own context for a NSOperation it works very well for me. I never call save when in the NSOperation.
Volker Am 01.03.2010 um 00:20 schrieb Rainer Standke: > Hello, > > I have an document-based CoreData application that uses an NSOperation to > manipulate ManagedObjects. I can successfully synchronize the main thread's > context, using mergeChangesFromContextDidSaveNotification:. > > However, when I subsequently try to save the document I get a warning that > the doc has been saved by another application. This happens in spite of the > fact that I update the doc's fFileModificationDate right after > synchronisation. > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
