On Oct 14, 2013, at 14:30 , Mike Abdullah <[email protected]> wrote:
> Therein lies your problem. You are modifying the document behind NSDocument's > back. Let the user/document system decide when to save, rather than saving > the context yourself. If you do desperately need to force a save, do so > through NSDocument, not the context. Ah. I think this is the result of my attempt to do something that's perhaps not supported, or maybe I'm just overriding the wrong things. The document that was giving me the trouble is a "Library" document my app implements. To edit an item in the library, I create a new document "ItemEditorDoc", and give it an NSManagedObjectContext that is a child of the LibraryDoc's MOC. (When the user saves the ItemEditorDoc, it should implicitly also save the LibraryDoc). Is this kosher? -- Rick
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
