#950: Error opening workspace file
----------------------------+-----------------------------------------------
Reporter: epatton | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.5.0
Component: wxGUI | Version: svn-develbranch6
Keywords: gui, workspace | Platform: Linux
Cpu: x86-64 |
----------------------------+-----------------------------------------------
I get the following error after trying to open a workspace file in Grass
6.5.svn:
{{{
Traceback (most recent call last):
File "/usr/local/grass-6.5.svn/etc/wxpython/wxgui.py",
line 622, in OnWorkspaceOpen
self.LoadWorkspaceFile(filename)
File "/usr/local/grass-6.5.svn/etc/wxpython/wxgui.py",
line 717, in LoadWorkspaceFile
lvdigit=layer['vdigit'])
KeyError
:
'vdigit'
}}}
This error only seems to manifest itself when layer group folders are
used.
To replicate error (in North Carolina dataset, Grass 6.5.svn):
1. start wxpthon gui, add vectors streams, lakes, geodetic_pts. Add raster
elevation.
2. Save the workspace.
3. Exit Grass, start Grass, load workspace, everything works ok.
4. add layer group folder, drag vectors into folder. Save workspace and
exit Grass.
5. Start Grass, load workspace; wxgui gives the same error as above.
Thanks Martin, all workspaces with nested folders can be saved and opened
normally in 6.4, 6.5 and trunk. The only problem I noticed was in trunk,
where vector line widths are displayed at a width of 1, not at the width
they were saved at in the original workspace file. In fact, the displayed
widths remain at 1 no matter what they are set at in the Properties
dialog. But other than that, everything looks great!
I've noticed a small error upon closer inspection; I've attached two
images illustrating the problem. In the first image
'Situation_Before.png', there are folders named Amundsen and Nahidik each
with many vector layers. They are child folders of the parent folder
Navgation. I save the workspace file, exit Grass, and restart, and open
the workspace file - the result is in the image 'Situation_After.png'. The
vectors that were inside the Amundsen and Nahidik folders are no longer
nested to the correct depth, and are now children of the Navigation
folder.
Replying to [comment:2 epatton]:
> Thanks Martin, all workspaces with nested folders can be saved and
opened normally in 6.4, 6.5 and trunk. The only problem I noticed was in
trunk, where vector line widths are displayed at a width of 1, not at the
width they were saved at in the original workspace file. In fact, the
displayed widths remain at 1 no matter what they are set at in the
Properties dialog. But other than that, everything looks great!
testing with trunk, r41161
* add vector map, set width to 2
* save workspace
* restart wxGUI
* open workspace
* width is set to 2
Replying to [comment:3 epatton]:
> I've noticed a small error upon closer inspection; I've attached two
images illustrating the problem. In the first image
'Situation_Before.png', there are folders named Amundsen and Nahidik each
with many vector layers. They are child folders of the parent folder
Navgation. I save the workspace file, exit Grass, and restart, and open
the workspace file - the result is in the image 'Situation_After.png'. The
vectors that were inside the Amundsen and Nahidik folders are no longer
nested to the correct depth, and are now children of the Navigation
folder.
Thanks Martin, I can confirm nested folders retain their positions after
reopening workspace files.
Can you confirm this behavior - I'm not sure what is happening here - if
you have a folder with a few layers inside, and drag the folder's position
around so it is above or below other folders or layers in the layer
manager, a layer always seems to get dropped from the folder after the
move is completed.
> Can you confirm this behavior - I'm not sure what is happening here - if
you have a folder with a few layers inside, and drag the folder's position
around so it is above or below other folders or layers in the layer
manager, a layer always seems to get dropped from the folder after the
move is completed.
>
> Should I file this under another bug?