gvSIG bugs #230
Eliminar llamdas al log de NullSpinnerHandler
| Status: | Closed | % Done: | 100% | |
|---|---|---|---|---|
| Priority: | High | Spent time: | - | |
| Assignee: |  Jorge Piera | |||
| Category: | - | |||
| Target version: | 2.0.0-alpha4 | |||
| Severity: | Add-on version: | 2.0.0 | ||
| gvSIG version: | 2.0.0 | Add-on build: | 2044 | |
| gvSIG build: | 2043 | Add-on resolve version: | 2.0.0 | |
| Operative System: | Add-on resolve build: | 2044 | ||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
En org.gvsig.tools.swing.impl.usability.spinner.date.NullSpinnerHandler.setValue se esta metiendo en el log el valor que se le asigna a cada vez. A este metodo se le invoca cientos de veces y provoca que el log se llene de trazas que no aportan ningun valor al desarrollador. Habria que quitar esas entradas del log.
Ya puestos, repasar el metodo entero, ya que parece que hay codigo redundante.
History
#1
Updated by Jorge Piera over 12 years ago
- Assignee set to Jorge Piera
#2
Updated by Joaquín del Cerro Murciano over 12 years ago
- Priority changed from Normal to High
#3
Updated by Jorge Piera over 12 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
- gvSIG build set to 2043
- Add-on version set to 2.0.0
- Add-on build set to 2044
- Add-on resolve version set to 2.0.0
- Add-on resolve build set to 2044
Removing the log.info lines and removing the not-necessary code
#4
Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed