Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden

References: 
 >Re: CoreData Property access compiles, but fails at runtime (From: Rick Mann <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.