This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Changes in PropertyPanel and PropertyEnv | ||
|---|---|---|---|
| Product: | platform | Reporter: | jrojcek <jrojcek> |
| Component: | Explorer | Assignee: | Jiri Rechtacek <jrechtacek> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | dstrupl, jtulach |
| Priority: | P1 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | TASK | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 23358 | ||
| Attachments: |
Proposed changes to PropertyPanel
New patch with accepted David's comments and unit tests written |
||
|
Description
jrojcek
2002-05-10 18:18:32 UTC
First step in defining this interface is to enhance the PropertyEnv to separate between asking for change of state and notifying that the change has been done. That means to add PropertyChangeListener support to already existing VetoableChange one. The second step is the ability to use PropertyPanel to control/obtain the value of the PropertyEnv.getState of the current property editor. Thus adding method PropertyPanel.getState () and firing property changes appropriatelly. Also there is a need to tell the property editor that it is about to be closed. For this purpose the PropertyPanel.updateState method should call the PropertyEnv associcated with the PropertyEditor and call setValid (STATE_VALID). Created attachment 5900 [details]
Proposed changes to PropertyPanel
When adding a listenter to the env please check that you either unregister the listener or use weak listener not cause a memory leak (then env holding references to the property panel). Created attachment 5906 [details]
New patch with accepted David's comments and unit tests written
The patch was applied. |