Re: Cocoa-dev Digest, Vol 6, Issue 133
Re: Cocoa-dev Digest, Vol 6, Issue 133
- Subject: Re: Cocoa-dev Digest, Vol 6, Issue 133
- From: Quincey Morris <email@hidden>
- Date: Fri, 23 Jan 2009 15:10:00 -0800
On Jan 23, 2009, at 14:27, Derek Kuhl wrote:
I was trying to adapt the iClass sample code to work in a document-
based form. The iClass example works great if you have the file
saved at runtime, but in documents they aren't saved right away. I
haven't been successful in migrating the document from an internal
private store into the public document store.
I haven't played with iClass, or looked at in any detail, but I'll
offer the following, FWIW:
Assuming that by "if you have the file saved at runtime" you're
referring to the fact that the standard untitled document you get with
NSPersistentDocument doesn't have a persistent store until after you
save it once, then, yes, that can make things difficult. IMO your best
strategy is to force the document to be named and saved once before
the user gets to see it.
If this issue is the only reason you needed to change iClass's
(presumably) working code for replacing the temporary object
references with permanent ones, then that strategy should pretty much
take care of the problem (at the the expense of never having any
"untitled" document windows).
Unfortunately, iClass looks like a rabbit-hole, and your version of it
is its own rabbit-hole, and it's going to be difficult to find anyone
who'll jump down those rabbit-holes with you. I think you'll have more
success getting answers on this list if you can narrow things down
even further to specific code fragments.
_______________________________________________
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