Re: Getting warning when saving merged MOC

2010-01-05 Thread Quincey Morris
On Jan 5, 2010, at 10:39, Rick Mann wrote: > I grant that I'm using NSPersistentDocument in a nonstandard way. I have a > Library of Parts (and a Group hierarchy). This Library is managed by a > LibraryDoc which inherits from NSPersistentDocument, and I consider this use > to be "standard." Whe

Re: Getting warning when saving merged MOC

2010-01-05 Thread Rick Mann
On Jan 5, 2010, at 05:30:59, Quincey Morris wrote: > On Jan 4, 2010, at 23:35, Rick Mann wrote: > >> I'm slowly but surely getting the hang of using multiple MOCs. I'm >> successfully creating objects in MOC B and merging those changes into the >> existing MOC A, and seeing the UI bound to MOC

Re: Getting warning when saving merged MOC

2010-01-05 Thread Quincey Morris
On Jan 4, 2010, at 23:35, Rick Mann wrote: > I'm slowly but surely getting the hang of using multiple MOCs. I'm > successfully creating objects in MOC B and merging those changes into the > existing MOC A, and seeing the UI bound to MOC A update to reflect the > changes. > > The problem I'm se

Re: Getting warning when saving merged MOC

2010-01-05 Thread Rick Mann
On Jan 5, 2010, at 00:07:55, Rob Keniger wrote: > > On 05/01/2010, at 5:35 PM, Rick Mann wrote: > >> Am I doing something wrong, or failing to take some step to avoid this >> confusion? There may be legitimate changes in MOC A that need to be saved, >> but the merged changes should already be

Re: Getting warning when saving merged MOC

2010-01-05 Thread Rob Keniger
On 05/01/2010, at 5:35 PM, Rick Mann wrote: > Am I doing something wrong, or failing to take some step to avoid this > confusion? There may be legitimate changes in MOC A that need to be saved, > but the merged changes should already be in the store. When doing things like this that you don't