I have a custom property editor component I would like to integrate with the
IDE. This can be done with EnhancedPropertyEditor. There is one problem:
My component needs to perform an action (pop up a palette) the first time it is
clicked. But my custom property editor is not actually instantiated until the
property editor field receives focus. So it always requires two clicks.
What I'd propose is an enhancement to the api for EnhancedPropertyEditor -
perhaps a "persistent" property that, when true, means that the property editor
will be instantiated for the life of the property sheet.
Target milestone -> 3.3
Target milestone -> 3.3.1.
Target milestone -> 3.4
Decreased priority - planning resources for 3.4
Target milestone was changed from '3.4' to TBD.
The solution to #24964 would also solve this request (as I hope). It
would allow you to specify a component for so called "read" state of
the property panel (in properyt sheet).
Making it duplicate of the mentioned issue. If you disagree that those
issues are in fact the same please reopen this one. Otherwise if you
are interested in progress please watch the other one.
*** This issue has been marked as a duplicate of 24964 ***
Uh, maybe...I'm not sure how hyperlinks relates to this, since I
don't imagine a hyperlink to be a property editor. But I'll take
your word for it.
BTW, if you look at the patch I submitted for the Options UI,
it includes an extension to PropertyEditor - getPersistentEditor()
which could solve the problem.
Tim, could you add a link at the patch for Options UI submitted by