Re: This document’s file has been changed by another application since you opened or saved it.
Re: This document’s file has been changed by another application since you opened or saved it.
- Subject: Re: This document’s file has been changed by another application since you opened or saved it.
- From: Kyle Sluder <email@hidden>
- Date: Mon, 14 Oct 2013 17:27:00 -0700
On Mon, Oct 14, 2013, at 04:46 PM, Rick Mann wrote:
>
> On Oct 14, 2013, at 15:37 , Jerry Krinock <email@hidden> wrote:
>
> > Creating a document to edit an item seems pretty weird. "Give it a child MOC" (setting its managed object context, I presume) from some other document seems even more weird. I would recommend a more conventional design.
>
> That's how I felt at first, but really, it should be fine. The user
> experience is that of editing an item (really, it's a part in a
> specialized CAD program, and the UI to edit it is virtually identical to
> that of editing a document that uses those parts). The UI includes a
> window with dirty status, undo stack, etc. It just doesn't save to a
> disk, but rather to the library's MOC. The new concurrency types
> encourage this use, I think.
The new concurrency types are explicitly designed around _not_ accessing
a persistent store via two different Core Data stacks.
Your intended UI sounds fine, but you should create a child MOC and
attach it to your document's main MOC. You should not be writing to the
on-disk store behind the document's PSC's back and then trying to patch
things up later.
>
> I have yet to adopt the new document convention of never having to save;
You should really get on board with that. It's been three OSes now. Do
not anticipate this option being available to you forever.
--Kyle Sluder
_______________________________________________
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