gvSIG bugs #89
Bad use of PropertyChangeSupport in AbstractDocument
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: | ||||
| Category: | Application | |||
| Target version: | 2.0.0-alpha3 | |||
| Severity: | Add-on version: | 2.0.0 | ||
| gvSIG version: | 2.0.0 | Add-on build: | 2042 | |
| gvSIG build: | 2042 | Add-on resolve version: | 2.0.0 | |
| Operative System: | Add-on resolve build: | 2043 | ||
| Keywords: | Proyecto: | |||
| Has patch: | Yes | Hito: | ||
| Add-on name: | unknown |
Description
The class org.gvsig.app.project.documents.AbstractDocument has a bad use of the PropertyChangeSupport:
lockandunlockdon't raises any event- Classes which extend of it cannot raise any event (propertyChangeSupport instance is private)
- Bad old values of
ownerandcommentare wrong (it's the new one!)
History
#1
Updated by Jorge Piera over 14 years ago
- Category set to Application
- Status changed from New to Fixed
- Assignee set to Jorge Piera
- Add-on version set to 2.0.0
- Add-on build set to 2042
- Add-on resolve version set to 2.0.0
- Add-on resolve build set to 2043
Fixed
- The propertyChangeSupport attribute is now protected.
- The events for the owner and comment properties raises the old values.
- lock and unlock raise an event.
[gvsig-desktop 37533]
#2
Updated by Joaquín del Cerro Murciano over 14 years ago
- Target version set to 2.0.0-alpha3
#3
Updated by Álvaro Anguix about 12 years ago
- Status changed from Fixed to Closed