Re: CoreData Property access compiles, but fails at runtime
Re: CoreData Property access compiles, but fails at runtime
- Subject: Re: CoreData Property access compiles, but fails at runtime
- From: Keary Suska <email@hidden>
- Date: Sat, 19 Jul 2008 10:29:45 -0600
- Thread-topic: CoreData Property access compiles, but fails at runtime
7/19/08 12:15 AM, also sprach email@hidden:
> I think this is also a bit of a red herring. I realize that my setEp1:
> is only being called because I instantiated this instance directly.
> When the instance is created by CoreData, my setEp1 is not called.
>
> This is odd, because I'm doing this successfully in a different entity
> (shadowing the CGPoint type).
>
> On Jul 18, 2008, at 22:38:23, Rick Mann wrote:
>
>> I have a CoreData entity called WireSegment, and a class to
>> implement it. A stripped-down version looks like this:
>>
>> @interface
>> WireSegment : NSManagedObject
>> {
>> }
>>
>> @property CGPoint ep1;
>> @property (retain) NSString* shadowEP1;
>>
>> @end
>>
>> @implementation WireSegment
>>
>> @dynamic shadowEP1;
You probably should be using @synthesize instead. Also, your transient
accessors are not properly formed--you should wrap actions (both get/set) in
will/did notification calls.
Best,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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