'Raises For Not Applicable Keys' not enough to step exception raises?
'Raises For Not Applicable Keys' not enough to step exception raises?
- Subject: 'Raises For Not Applicable Keys' not enough to step exception raises?
- From: "Sean McBride" <email@hidden>
- Date: Tue, 6 May 2008 11:51:49 -0400
- Organization: Rogue Research
Hi all,
I have an app that uses an NSOutlineView bound to an NSTreeController in
entity mode. The tree controller matches all 'Shape' entities, but
there are also sub-entities named 'Square' and 'Circle'. I have a
master-detail UI. All 'Shapes' have a 'name' attribute and there is no
problem there. Only 'Circle' has a 'radius' attribute however, and I
want to show this in a textfield. I've bound the textfield and
unchecked the 'Raises For Not Applicable Keys'.
The problem is that I'm still getting an NSException raised. It's
raised from [Circle valueForUndefinedKey:]. 'Circle' is an
NSManagedObject subclass.
Does one also have to implement valueForUndefinedKey: in this
situation? I thought removing 'Raises For Not Applicable Keys' was
supposed to be sufficient.
Thanks,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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