I have found and fixed the problem with getting two extra objects instead of 
one, and have gone through all my code yet again, and I think I am down to 2 
issues:

1. When I do a save, then Save As, then Save As again, I get a message that one 
of my objects has been invalidated. I haven't edited it or anything, so I 
really don't know what could have happened to it. And it really sounds strange 
that it's only on the second Save As that things start going awry. Any ideas 
what could be causing this?

2. When I open a file, and then do a Save As, it gives me an error:

AppKit called 
rmdir("/private/var/folders/nl/nlcXN-oPHJiAXXc1Z0R5VE+++TI/TemporaryItems/(A 
Document Being Saved By NovaMind5TP 116)"), it didn't return 0, and errno was 
set to 66.

I can't reproduce either of these issues on my mini test project, so there has 
to be something hidden in the code of my main application. I have no idea where 
to look for these issues.

Any ideas?

I'm still incredibly frustrated by the hidden workings of CoreData, which have 
now cost me a month of work just to get saving and loading (mostly) working 
with a custom store.

Any suggestions would be very welcome.

Gideon

On 20/03/2010, at 7:04 PM, Gideon King wrote:

> During the course of the Save As operation, core data creates a temporary 
> clone of my managed objects, which appears to be part of its normal way of 
> doing things (I can replicate this in a test project), but in the case of my 
> project it is creating *two* clones of all my objects. One has the metadata 
> in it, and the other one has all my data in it, but no metadata.
> 
> Anyone have any idea why it would be creating two new sets of managed objects?
> 
> TIA
> 
> Gideon
> 

_______________________________________________

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]

Reply via email to