Note that generally these flags may or may not be supported in
future versions. The following flags may be passed to the JVM
in the form
runide -J-Dsome.property=true which
affect the user interface of the Property Sheet. Generally they
represent either cases where different applications have different
requirements, or where there is some contention about which style
is the most effective.
The Property Sheet will look for a number of custom values in UIManager, which may be supplied to affect its appearance, either by a themes.xml file in the user directory, or by a custom look and feel. It is not required that UIManager return non-null for any of these values - they are optional for enhancing the presentation of the Property Sheet:
netbeans.ps.combohack-Forces the combo box editor to use a heavyweight popup window, used to solve a problem with some window managers.
netbeans.ps.forcetabs-Force each property set to be displayed in a separate tab (normally this is done only by providing a hint from a PropertySet via getValue("tabName").
netbeans.ps.nevertabs-Disable use of tabs in the Property Sheet even if the property set provides a tab name via the above mentioned hint
The PropertyPanel component is a generic component which will display a
property editor for a single property - rather like a single cell of the
Property Sheet. There are a few non-normative client properties which may
be set on it to change its behavior, via
radioButtonThreshold-Integer - display a set of labelled radio buttons instead of a combo box if the property editor returns less than the specified number of tags from
suppressCustomEditor-Do not display a custom editor button even if the property's associated property editor supports one
useLabels-Use the property's display name as the label portion of a checkbox boolean editor, if the property is boolean, so that there is some indication of keyboard focus. If radioButtonThreshold is in use and a property panel will display radio buttons, this will also affect whether a TitledBorder is used for the group of radio buttons.
PropertySet.getValue("tabName")will be aggregated together on the same tab.
To use this functionality in a
standalone application, an implementation of
be available via
Lookup.getDefault(). For an example, see
A non-functional implementation is provided if none is present via lookup,
to enable unit testing.