What can be in an IB Plugin?
What can be in an IB Plugin?
- Subject: What can be in an IB Plugin?
- From: Rick Hoge <email@hidden>
- Date: Thu, 22 Nov 2007 08:33:55 -0500
I noticed that if I add a library object to an IB 3.x Plugin that is a
standard Cocoa object (e.g. an NSPopupButton with some extra
configuration) that the class is not displayed in the inspector after
I select it - the drop-down list shows NSPopupButton as an option but
after I select it the class field is blank. Adding a custom subclass
to the linked framework makes this weirdness go away.
Do all added objects *have* to be custom subclasses? What if, as in
the above example, I just want a standard NSPopupButton that is pre-
populated with a bunch of selections, without requiring a custom
subclass. Is the IBPlugin the best way to do this? Many of my
intended uses for the plugin definitely require custom subclasses.
However in some cases it may be convenient to have some aggregate view
collection that requires configuration, and which I want to be
consistent in different contexts, but which does not actually require
any subclasses.
thanks for any info on this,
Rick
_______________________________________________
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