Re: can Interface Builder be extended with palettes of our own custom Carbon controls?
Re: can Interface Builder be extended with palettes of our own custom Carbon controls?
- Subject: Re: can Interface Builder be extended with palettes of our own custom Carbon controls?
- From: Andreas Grosam <email@hidden>
- Date: Sat, 16 Sep 2006 18:44:07 +0200
On 09.09.2006, at 00:40, Eric Schlegel wrote:
On Sep 8, 2006, at 3:18 PM, Rick Sustek wrote:
There seems to be indications this is possible.
But I haven't found enough concrete evidence in the 'Help', 'FAQ', or
this mailing list, to know for sure this doable and well supported.
No, IB does not support extensible palettes for Carbon controls, just
for Cocoa.
It is even impossible to specify a ClassID if you wish to subclass a
system control - simply because of the fact that there is no field
where you can type it in - except for a raw HIView, Custom Control and
Window.
So, if you want to subclass a BevelButton for instance, you need to use
a plain HIView to in order to be able to specify a custom ClassID. Too
bad, in this case you are not able to specify all other parameters
associated to a BevelButtom, since the inspector panel for a HIView
does not know anything about BevelButtons. So, you have to set all
parameters in your code programmatically anyway. Furthermore, if you
test your interface directly in IB, you get a bunch of nice default
HIViews drawn, that is you see nothing.
IMHO, as it is presently when working with IB, you get no advantage
when subclassing from existing system controls - in particular if your
overriden version does not completely change behavior and look of the
base control. It seems to be better to search the control by ID and
then to just install event handlers programmatically somewhere in the
window code, in order to provide "subclassing" and initialization with
custom data.
However, I would appreciate it - or better I would love it - if the
apple devs would do us a favor and just add a "Custom" panel to each
system control -- much like it is already done for the Window control.
I don't think this would have any implications - except the desired
one.
Andreas
-eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden