Re: Using NSKeyedArchiver to save and restore state on iPhone apps
Re: Using NSKeyedArchiver to save and restore state on iPhone apps
- Subject: Re: Using NSKeyedArchiver to save and restore state on iPhone apps
- From: Jason Bobier <email@hidden>
- Date: Wed, 10 Feb 2010 19:17:48 -0500
Yes, you have to account for any references into the unarchived graph that objects not included in the graph hold. In my case, this should be as simple as removing the navcontroller view from it's superview.
Jason
On Feb 10, 2010, at 4:19 PM, Kyle Sluder wrote:
> On Wed, Feb 10, 2010 at 12:54 PM, Jason Bobier <email@hidden> wrote:
>> All of these are NSCoding compliant, which means that if I archive it, I should be able to unarchive it and get the exact state back (subject to conditional archiving, etc...) as long as I archive a complete object graph.
>
> Not true. You have no idea what other objects have references to the
> ones you've archives, and these external references might be crucial
> to the functionality of your object graph.
>
> --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