gvSIG bugs #2229
Error saving project if OSM layers are included
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Urgent | Spent time: | - | |
| Assignee: |  Ignacio Brodín | |||
| Category: | OSM | |||
| Target version: | 2.1.0-2218-testing | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2216 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
Trying to save a project including OSM layers produces an error (see attached screenshot).
gvSIG.log (46.9 KB)
save-project-error.png (18.6 KB)
save-project-error2.png (7.04 KB)
test3.gvsproj (14.1 KB)
gvSIG.log (4.71 KB)
History
#1
Updated by Cesar Martinez Izquierdo over 10 years ago
- File save-project-error2.png added
- File test3.gvsproj added
- File gvSIG.log added
The project file is actually created, but it seems to be unreadable for gvSIG afterwards (see attached screenshot with the error + project file + log).
#2
Updated by Álvaro Anguix over 10 years ago
- Category set to OSM
- Assignee set to Ignacio Brodín
- Priority changed from Normal to Urgent
- Target version set to 2.1.0-2218-testing
#3
Updated by Ignacio Brodín over 10 years ago
- Status changed from New to Fixed
I did some changes in the persistence some days ago and now it works in my workspace. Alvaro, could you test it with the packages that I sent you? Those changes are not in the build 2217 but it will come out in the next build (2218). I set the target version to the 2218 to test it again.
#4
Updated by Álvaro Anguix over 10 years ago
Con el 2217+nuevo raster me funciona correctamente.
#5
Updated by Álvaro Anguix over 10 years ago
- Status changed from Fixed to Closed