question: a propertyeditor may choose to make available a full custom component that edits its property value . it is the responsibility of the propertyeditor to hook itself up to its editor component itself and to report property value changes by firing a propertychange event . the higher-level code that calls getcustomeditor may either embed the component in some larger property sheet , or it may put it in its own individual dialog , or ... concode_field_sep BoxSizingValueConverter valueConverter concode_elem_sep PropertyChangeSupport propertyChangeSupport concode_elem_sep BoxSizing value concode_field_sep String getJavaInitializationString concode_elem_sep Object getValue concode_elem_sep boolean supportsCustomEditor concode_elem_sep void setValue concode_elem_sep void paintValue concode_elem_sep String[] getTags concode_elem_sep String getAsText concode_elem_sep void addPropertyChangeListener concode_elem_sep void removePropertyChangeListener concode_elem_sep boolean isPaintable concode_elem_sep void setAsText
target: Component function ( ) { return null ; }