It's probably unrelated, but why are you using NSArchiver? There's almost no
need to these days, and it's more-or-less deprecated (not available on the
iPhone for example).
On 14 Dec 2009, at 12:41, Richard Somers wrote:
> I have a Core Data document based application.
>
> Saving the file as XML or SQLite works fine.
>
> Saving as binary results in an error: *** -[NSKeyedArchiver
> encodeValueOfObjCType:at:]: this archiver cannot encode structs.
>
> The struct in question is a transformable attribute using a custom value
> transformer.
>
> - (id)transformedValue:(id)value
> {
> return [NSArchiver archivedDataWithRootObject:value];
> }
>
> No where in my code do I call NSKeyedArchiver.
>
> Why does the core data framework work fine saving as XML or SQLite but not
> binary?
>
> --Richard
>
> _______________________________________________
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> 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/cocoadev%40mikeabdullah.net
>
> This email sent to cocoa...@mikeabdullah.net
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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 arch...@mail-archive.com
