| Property change event not persisting its value? [message #607739] |
Thu, 12 May 2005 02:48 |
Eclipse User |
|
|
|
In my customizer, I have an "Apply" button that I use to do a
firePropertyChange(...) to update of the bean.
My log shows that it is the WindowLaucher that is registering on the
customizer for property change events:
2005-05-11 21:46:20,793 [Connection Thread] DEBUG
net.certiv.swing.GradientCustomizer - Adding property change listener
for: org.eclipse.ve.internal.java.remotevm.WindowLauncher$5
When I click the apply button, VE *does* repaint the bean in the design
view to conform to the changed value provided by the customizer. VE
does not, however, update the property sheet or the code.
If I then click VE's "OK" button, the code and property sheet update
correctly (the customizer also closes, which is not the desired
behavior).
If, instead, I click VE's "Cancel" button, the bean repaints back to its
original state; the property sheet and code are unchanged.
While the display and code/property sheet are out of sync, the getter
methods do appear to return the displayed values, rather than the
code/property sheet values. So, it appears that VE is imposing state on
the operation of the customizer.
My customizer handles its own checkpoint state issues - it is a rather
complete JTable-based form designer for the JGoodies form layout manager
that supports visual prototyping with checkpoint saves as the user
progresses through the design. Closing and reopening the customizer
just to persist changes is not desirable.
Is there a way to have VE simply persist a changed property value
whenever its property change event is fired? The alternative is for me,
and others similarly situated, to modify the customizer to dig into the
BeanPropertyEditorJFrame to access notifySavePropertyValue() and other
methods directly. Is there a better approach?
Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.20106 seconds
Home