Re: IB3 Plugin Troubles
Re: IB3 Plugin Troubles
- Subject: Re: IB3 Plugin Troubles
- From: Jonathan Hess <email@hidden>
- Date: Thu, 31 Jul 2008 22:22:03 -0700
Hey Seth -
Sorry to hear that you're having troubles.
On Jul 31, 2008, at 9:38 PM, Seth Willits wrote:
Howdy,
I have my own segmented view control that I wrote to support various
styles and behaviors I just can't get from the standard one. It
turns out I use this control fairly frequently so I want to create
an IB plugin for it. I've started making it (it's been very slow
going) and I'm running into a few problems.
- ibPreferredDesignSize / ibMinimumSize / ibPreferredResizeDirection
all seem to be completely ignored.
ibPreferredDesignSize and ibPreferredResizeDirection are both used to
implement the size to fit action from the layout menu. Right now
Interface Builder really only uses ibMinimumSize in one case, when one
of the dimensions is equal to the same dimesion provided by
ibMaximumSize. In this case, IB prevents resizing along that axis. For
example, if your segmented control is not vertically resizable, then
implement ibMaximumSize, and ibMinimumSize to return the same value
for the height of the control. This will prevent vertical resizing of
the control. Right now there is no way to declare that the control
cannot be resized to a width less than some specific value. This may
change in the future, and if it does, the results of these methods
will be used to limit the resizing.
- isChildInitiallySelectable is also ignored. With no current
selection, if I click on my control, it selects one of the segments,
rather than the control first.
If you have an design window open and key, then there is always a
selection. This method is used when there's a click on an object when
its parent (the segmented control in this case) isn't active. You can
tell if an object is active by the appearance of a dark ring. The
easiest way to see dark ring would be to add an NSBox to a window, and
then double click on it. Are you implementing
isChildInitiallySelectable on the segmented control, and returning NO
for the segment objects, or did you by chance accidently implement the
method on the segment objects? IB certainly uses these methods to
govern selection behavior, for example, they're used by NSTableView to
prevent the initial selection of the table view's columns with a
single click. How does the behavior your seeing differ from a table
view for example?
- I can't figure out how to get an inspector for my cell to appear
in the Sizing panel of the Inspector window. Like
NSSegmentedControl, my segments can have independent widths so I
want to stick the sizing information in there.
Ideally, you would be able to introduce an inspector into any of the
inspector modes. Right now the public API only allows for insertion
into the attributes inspector mode.
I have some other things as well, but these I've been exploring for
quite a long time and I can't figure out.
As you find issue, please file bugs at bugreport.apple.com. Especially
when your run into limitations of the API. If you file a report with
your isChildInitiallySelectable issue, and include an example, I'll do
my best to clear things up for you.
Good Luck -
Jon Hess
Any help would be appreciated,
--
Seth Willits
_______________________________________________
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
_______________________________________________
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