public interface ExPropertyEditor extends PropertyEditor
PropertyEnvinstance is typically used to set the valid/invalid state of the property, and to retrieve a reference to the Node.Property or PropertyDescriptor for the property being edited.
|Modifier and Type||Field and Description|
If you want to enable/disable the OK button on the custom property editor panel you can fire a property change event with boolean value.
If you want to add custom help ID on the custom property editor panel you can store its value in PROPERTY_HELP_ID property.
|Modifier and Type||Method and Description|
This method is called by the property sheet to pass the environment to the property editor.
addPropertyChangeListener, getAsText, getCustomEditor, getJavaInitializationString, getTags, getValue, isPaintable, paintValue, removePropertyChangeListener, setAsText, setValue, supportsCustomEditor
static final String PROP_VALUE_VALID
static final String PROPERTY_HELP_ID
void attachEnv(PropertyEnv env)
env.getFeatureDescriptor().getValue (String key)to retrieve any hints the Property object may supply regarding how the property editor should behave (such as providing alternate text representations of "true" and "false" for a Boolean property editor).
Property editors that support an invalid state (typically
used to disable the OK button in custom editor dialogs) should cache
the env object and update the env's state on calls to
Note: This method may be called more than once
during the lifetime of a property editor. In particular, custom
property editors which want to change the state of the OK button by
should not assume that the instance of PropertyEnv most recently
passed to attachEnv() on the underlying property editor is the same
instance that controls the dialog they are displayed in. Custom
editors which wish to control the state of the OK button should cache
the last-set PropertyEnv at the time they are instantiated.
Built on January 23 2023. | Copyright © 2017-2023 Apache Software Foundation. All Rights Reserved.