Re: Problems with custom NSView subclass, IBPalette, and bindings support
Re: Problems with custom NSView subclass, IBPalette, and bindings support
- Subject: Re: Problems with custom NSView subclass, IBPalette, and bindings support
- From: "Sean McBride" <email@hidden>
- Date: Thu, 27 Jan 2005 11:11:18 -0500
- Organization: Rogue Research
On 2005-01-26 10:29, mmalcolm crawford said:
>> Should I call super at the beginning or end of my implementation?
>>
>I don't think it matters.
In fact it does... I'm having all kind of problems with my NSView class,
and I've been basing myself on your GraphicsBindings example. After a
lot of trial and error, I came to try adding the call to super in
GraphicsView's bind:...
If I add:
[super bind:bindingName toObject:observableObject withKeyPath:
observableKeyPath options:options];
to the start I get:
2005-01-27 10:52:07.053 GraphicsBindings[853] [<GraphicsView 0x35e230>
setValue:forUndefinedKey:]: this class is not key value coding-compliant
for the key graphics.
If I add it to the end all seems well. I think I more or less understand
why this makes sense.
>> Am I blind, or is this not documented? Your GraphicsView.m and
>> JoystickView.m classes in you GraphicsBindings example also do not call
>> super. Is doing so only needed if one is making an IBPalette?
>No, it's not documented. Please file an enhancement request.
<rdar://3977143>
As I'm having problems getting my own class to work, I've decided to
instead start by making a palette for your GraphicsBindings example.
I'll send it to you when I'm done so you can make it public for others,
if you'd like...
Thanks again,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden