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: Rick Mann <email@hidden>
- Date: Fri, 18 Jul 2008 23:15:40 -0700
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;
- (CGPoint)
ep1
{
NSString* v = self.shadowEP1;
NSPoint nsP = ::NSPointFromString(v);
return ::NSPointToCGPoint(nsP);
}
- (void)
setEp1: (CGPoint) inVal
{
NSString* v = ::NSStringFromPoint(::NSPointFromCGPoint(inVal));
self.shadowEP1 = v;
}
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 model, ep1 is a transient undefined attribute, and
shadowEP1 is an NSString.
Any suggestions as to what's wrong? Thanks!
--
Rick
_______________________________________________
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
--
Rick
_______________________________________________
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