gvSIG bugs #1370
Import fields doesn't work in gvSIG 1.12
Status: | New | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | |||
Assignee: | - | |||
Category: | - | |||
Target version: | - | |||
Severity: | Add-on name: | Unknown | ||
gvSIG version: | 1.12.0 | Add-on version: | ||
gvSIG build: | 1417 | Add-on build: | ||
Operative System: | Windows | Add-on resolve version: | ||
Keywords: | Add-on resolve build: | |||
Has patch: | No |
Description
Import fields doesn't work in gvSIG 1.12. It returns the following java.lang.ClassCastException:
DEBUG AWT-EventQueue-0 com.iver.andami.messages.NotificationManager - java.lang.ClassCastException: com.iver.cit.gvsig.project.documents.table.gui.Table cannot be cast to com.iver.cit.gvsig.project.documents.view.gui.View java.lang.ClassCastException: com.iver.cit.gvsig.project.documents.table.gui.Table cannot be cast to com.iver.cit.gvsig.project.documents.view.gui.View at com.iver.cit.gvsig.StartEditing.startCommandsApplicable(StartEditing.java:200) at com.iver.cit.gvsig.layers.VectorialLayerEdited.activationGained(VectorialLayerEdited.java:567) at com.iver.cit.gvsig.EditionManager.activationChanged(EditionManager.java:107) at com.iver.cit.gvsig.fmap.layers.FLyrDefault.callActivationChanged(FLyrDefault.java:777) at com.iver.cit.gvsig.fmap.layers.FLyrDefault.setActive(FLyrDefault.java:269) [...]
This issue was reported by Ernesto Sferlazza in gvSIG Italian mailing list:
https://gvsig.org/lists/pipermail/gvsig_italian/2012-November/003258.html
History
#1
Updated by Francisco Puga over 11 years ago
Nobody touch the Import Fields Extension so i think that the bug was there for long time.
These kind of bugs related to have a Table open over a View are so common in gvSIG. I proposed an API change to avoid this some time ago but it was rejected.
http://joinup.ec.europa.eu/mailman/archives/gvsig-desktop-devel/2011-July/000381.html
In any way, can you paste a bit more of the log to see where is the line of the Import Field extension where the error begins.
Thanks
#2
Updated by Antonio Falciano over 11 years ago
Hi Francisco, you're right! I've just verified that this bug was since gvSIG 1.11, however it happens only with temporary layers (for instance, those deriving from "Create random vector layer" SEXTANTE tool) and maybe it could depend by how SEXTANTE create a new view. In order to reproduce it, you can create two random layers with the same number of features (for instance, one of points and other of polygons): they share the same ID field, so we need to add and populate a new field in the first alphanumerical table and try to import into the second one. The bug occurs in this case, while if the layers are saved locally not. Cheers.
#3
Updated by Álvaro Anguix over 10 years ago
- Project changed from Application: gvSIG desktop to | gvSIG desktop 1