gvSIG bugs #2885
Map size is locked when its window is maximized
Status: | Won't fix | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | Cesar Martinez Izquierdo | |||
Category: | Document layout | |||
Target version: | 2.2.0-2309 | |||
Severity: | Major | Add-on version: | ||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | 2250 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | Proyecto: | |||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
The map size is locked sometimes when its window is maximized (at least in Windows).
If I close and reopen the map document, the map is shown correctly.
See the screenshot in attachment. There's not trace of error in the gvSIG.log.
History
#1 Updated by Álvaro Anguix almost 10 years ago
En Linux también me ocurre.
#2 Updated by Álvaro Anguix over 9 years ago
- Target version set to 2.2.0-2311-rc2
- Assignee set to Cesar Martinez Izquierdo
#3 Updated by Cesar Martinez Izquierdo over 9 years ago
- Status changed from New to Fixed
#4 Updated by Cesar Martinez Izquierdo over 9 years ago
Some changes have been done in the layout drawing in order to fix #2905. These changes may have corrected also this bug, but it is difficult to confirm as the bug can't be systematically reproduced. Please, reopen the ticket if it happens again to you.
#5 Updated by Álvaro Anguix over 9 years ago
- Target version changed from 2.2.0-2311-rc2 to 2.2.0-2307 (rev. org.gvsig.desktop-2.0.94)
#6 Updated by Álvaro Anguix over 9 years ago
- Status changed from Fixed to Closed
#7 Updated by Antonio Falciano over 9 years ago
- Status changed from Closed to New
Hi Cesar,
it happens in build 2308 on Windows 7 in the same way and the only workaround consists into closing and reopening the map document. Cheers.
#8 Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version changed from 2.2.0-2307 (rev. org.gvsig.desktop-2.0.94) to 2.3.0-2400 (rev. org.gvsig.desktop-2.0.102)
#9 Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version changed from 2.3.0-2400 (rev. org.gvsig.desktop-2.0.102) to 2.2.0-2310
#10 Updated by Cesar Martinez Izquierdo over 9 years ago
I have not been able to reproduce it on Windows 7, build 2308. It would be very helful if you can isolate the sequence of steps necessary to systematically reproduce it, as it is otherwise very difficult to debug the error.
#11 Updated by Antonio Falciano over 9 years ago
Hi Cesar,
you're right. This issue is very difficult to reproduce, because it seems to happen randomly. If you like, we can close the ticket and reopen it only when it can be reproduced in some way. Thank you for the try. Cheers, Antonio
#12 Updated by Álvaro Anguix over 9 years ago
- Status changed from New to Won't fix
Ok, Antonio. I change it to "won't fix"
#13 Updated by Joaquín del Cerro Murciano over 9 years ago
- Target version changed from 2.2.0-2310 to 2.2.0-2309