Re: Make Custom Struct Key-Value Coding Compliant
Re: Make Custom Struct Key-Value Coding Compliant
- Subject: Re: Make Custom Struct Key-Value Coding Compliant
- From: Richard Somers <email@hidden>
- Date: Wed, 15 Feb 2012 17:04:10 -0700
SOLVED - Thanks for all the comments.
On Feb 11, 2012, at 11:56 PM, Graham Cox wrote:
> Making it an object is easy and usually it turns out that the desire to resist doing that is misguided, based on some faulty assumptions.
I decided to resist no longer and make my custom strut an object. I made an object that had individual properties corresponding to the struct members. Unfortunately this created to many problems elsewhere.
But the story has a happy ending. Arbitrary structs are Key-Value Coding compliant and work fine with Core Data, they do not need to be stored in the managed object as an object. The documentation is in error on this point.
On Feb 12, 2012, at 2:18 AM, Joar Wingfors wrote:
> Please file a bug report on the documentation:
Filed bug report Bug ID# 10872122.
On Feb 12, 2012, at 6:50 AM, John Joyce wrote:
> But the best advice, don't fight the framework.
Agreed. Originally I thought that custom structs were not compatible with Core Data. But this is not true. They can work very well with the framework.
Thanks again.
--Richard
_______________________________________________
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