if you have the @property statement, and you use the I think @synthesize (could be wrong about that) you don't need to write the functions yourself. Try taking out the @property statement.
On Wed, Jul 2, 2008 at 10:13 AM, Milen Dzhumerov <[EMAIL PROTECTED]> wrote: > Hi all, > > I've run into a something I find strange. I've got a property declared as: > > @property(readwrite, assign, nonatomic) CGImageRef image; > > And it's implemented as: > > -(CGImageRef)image > { > return mImage; > } > > -(void)setImage:(CGImageRef)newImage > { > if(mImage != newImage) > { > CGImageRelease(mImage); > CGImageRetain(newImage); > mImage = newImage; > } > } > > When I try to set it using KVC (e.g. [obj setValue:[NSValue > valueWithPointer:image] forKeyPath:@"image"]), it says [<*ClassName* > 0x133050> setValue:forUndefinedKey:]: this class is not key value > coding-compliant for the key image.' > > Any hints on why the class is not KVC-compliant? I've read the docs and it > seems to satisfy the bullet points listed (moreover it's even declared as > @property so the naming of the setters / getters should be alright). > > Thanks, > M > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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/bobber205%40gmail.com > > This email sent to [EMAIL PROTECTED] > -- If you can't be kind, at least have the decency to be vague. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]