The new PropertySheet implementation provides a
InplaceEditor that *tries* to work with the
supplied by this interface. Since the contract for
taking the value is now pressing Enter, not just
for a FOCUS_LOST event, I've done some very weird
with introspecting addActionListener methods and
focus lost events to get it to work.
However, these hacks are not always reliable, and
of the combo box does not match the other combo
the property sheet.
This class could easily be rewritten as an
and get rid of the custom editor component entirely -
just return TRUE from
and supply any matching methods from getTags.
As discussed in issue 26367, the functionality of custom in-place
editor still cannot be substituted by standard means. We need to
investigate this further.
See my comments to issue 26367 - this should be possible as soon as I
merge the PropertyPanel rewrite branch.
FYI, you can now supply an initial value for editing via
(it must be a string). So that should take care of the last reason we can't kill the older
Note: Be *careful* not to return anything from getValue('initialEditValue") if the event
handler already has a real event handler you want to show - the editors will prefer the
initial value to anything they get from the property editor, so you only want to do this
when the property value has not been set to a real value.
Done. The custom in-place editor eliminated.
new revision: 1.18; previous revision: 1.17
Amen! Welcome to the brave new world!