Interface Builder Palettes Collide
Interface Builder Palettes Collide
- Subject: Interface Builder Palettes Collide
- From: Daniel Jalkut <email@hidden>
- Date: Tue, 3 Jun 2003 18:05:19 -0700
If two palettes in Interface Builder implement the same class, does
Interface Builder do anything to keep the palettes' namespaces
separate? I'm asking because I'm getting funky behavior that I believe
is caused by my having two custom palettes - one that implements a
custom control inspector/palette, and another that implements a more
complex view that *contains* an instance of the custom control.
To make these palettes "stand-alone", I just compile in the custom
control class code to each palette. I suspect that Interface Builder
is getting confused, and when the time comes to ask the custom view who
its inspector is, it's asking the wrong implementation. Shouldn't IB
be able to limit its querying of classes to the class definition for
the particular palette? Or is this asking too much of the ObjC runtime?
I suppose I may have to create a Framework containing the control's
class, and have both palettes link against that?
Thanks for any feedback,
Daniel
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.