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: | PropertyChangeEvents are not always fired | ||
---|---|---|---|
Product: | java | Reporter: | Svata Dedic <sdedic> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | raccah |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Patch that solves this problem |
Description
Svata Dedic
2001-04-25 12:52:15 UTC
Created attachment 1245 [details]
Patch that solves this problem
The cause is that PropertyChangeSupport.firePropertyChange compares old and new property's values and if they are equal it does not fire anything. In this particular case, this optimization blocks the events from being delivered. I dare not to change Identifier's equals method to include the indicated resolution state. Identifiers are used at many places throughout the IDE. Instead of that, I would patch the ElementImpl class to not use the standard PropertyChangeSupport, but I've copied the necessary code to handle listener list, sychronization and event firing. Please see & comment the attached diff file. Target milestone -> 3.3 Changing milestone to 3.2.1, this should be fixed for the sake of tools built on top of NetBeans Setting milestone forth (it's still not integrated). Marking as FIXED (in dev trunk only) VERIFIED Resolved for 3.4.x or earlier, no new info since then -> closing. |