Re: Subclassing breaks bindings?
Re: Subclassing breaks bindings?
- Subject: Re: Subclassing breaks bindings?
- From: Dalzhim Dalzhim <email@hidden>
- Date: Wed, 13 May 2009 12:22:28 -0400
Thanks Alexander, you made me realize my NSCell subclass was already
instantiated as a NSPopUpButtonCell when I dragged the NSPopUpButton into my
nib in Interface Builder. I have changed the NSCell subclass for my own and
now I can get both the binding and the custom appearance to work in my
simplified test.
Although I have stumbled upon a new problem. When supplying a NSMenu in
which the NSMenuItem all have Actions and Targets, the binding doesn't get
triggered! Is that really how it is supposed to be?
Thanks
-Dalzhim
2009/5/13 Alexander Spohr <email@hidden>
> Oh sorry, I missed your cellClass problem in my first post :(
>
> Am 13.05.2009 um 17:56 schrieb Alexander Spohr:
>
> If I try to add a NSPopUpButton to my nib instead of a custom view, and
>>> set
>>> it's class to MySubclass, then the bindings work fine, but my override on
>>> +
>>> (Class) cellClass doesn't seem to work.
>>>
>>> Can anyone help me figure out what I might be doing wrong?
>>>
>>
> If cellClass is used in initWithFrame: only you might override
> initWithCoder: and set the cell(s class) there.
>
> atze
>
>
_______________________________________________
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