You probably should be using @synthesize instead
For modeled Core Data properties, @dynamic is better.
- Ben
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the mod
On Jul 19, 2008, at 09:29:45, Keary Suska wrote:
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.
Without specifying, they default to @dynamic, which means I'm
7/19/08 12:15 AM, also sprach [EMAIL PROTECTED]:
> 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 t
I forgot to set the class name in the model editor. D'oh.
On Jul 18, 2008, at 22:38:23, Rick Mann wrote:
When executing the line
self.shadowEP1 = v;
I get the following in the console:
-[WireSegment setShadowEP1:]: unrecognized selector sent to
instance 0x1067600
In the CoreData
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
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
@d
