On mac, in today's (Aug 16) update it crashes wxGUI when I have a raster
(elevation) and a vector (roadsmajor) in map layer list and I switch to 3D
view. It does not crash when there is only raster elevation. Helena
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Changes (by helena):
* cpu: x86-64 => OSX/Intel
Comment:
More details about this for trunk compiled March 26, 2011:
entire wxGUI crashes after adding vector points or lines, it gives the
following error when trying to switch to 3D view
with both elevation and vector layer selected (using nc_spm data set, I
had elevation and point firestations
in map layers list, but it gives the error for line vector busroutes as
well)
{{{
(Traceback - no module named adw.advancedsplash)
v.info <t> is not a valid flag
is it trying to run v.info -t?
}}}
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Comment(by hamish):
Replying to [comment:5 helena]:
> but it gives the error for line vector busroutes as well)
>
{{{
> (Traceback - no module named adw.advancedsplash)
> v.info <t> is not a valid flag
> is it trying to run v.info -t?
}}}
v.info printing flags were changed in trunk. I quite disagree with that
change and would like to revert it before too long, as it introduces a
contextual meaning extra level of abstraction to learn/deal with, makes
life harder for command line users while offering dubious advantage to the
module's GUI users, fixes what wasn't broken in the first place, and makes
the module inconsistent with other core module usage (which IMNSHO should
not be moved away from flags either, and certainly not without widespread
positive feedback/consensus).
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Comment(by martinl):
Replying to [comment:6 hamish]:
> v.info printing flags were changed in trunk. I quite disagree with that
change and would like to revert it before too long, as it introduces a
contextual meaning extra level of abstraction to
I was just waiting for some discussion, more opinions. I received only
yours negative one and nothing more. So I will revert changes `v.info` at
this point.
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Comment(by martinl):
Replying to [comment:6 hamish]:
> to learn/deal with, makes life harder for command line users while
offering dubious advantage to the module's GUI users, fixes what wasn't
broken in the first place, and makes the module
btw, here should be used `grass.vector_topo_info()`
inconsistent with other core module usage (which IMNSHO should not be
moved away from flags either, and certainly not without widespread
positive feedback/consensus).
In other words without any feedback (except yours negative), doesn't
matter if positive.
Replying to [comment:8 martinl]:
> Replying to [comment:6 hamish]:
> > to learn/deal with, makes life harder for command line users while
offering dubious advantage to the module's GUI users, fixes what wasn't
broken in the first place, and makes the module
>
> btw, here should be used `grass.vector_topo_info()`
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: martinl
Type: defect | Status: assigned
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Comment(by martinl):
Replying to [comment:4 helena]:
> On mac, in today's (Aug 16) update it crashes wxGUI when I have a raster
(elevation) and a vector (roadsmajor) in map layer list and I switch to 3D
view. It does not crash when there is only raster elevation. Helena
#1126: 3D view crashing when started with vector data
-----------------------+----------------------------------------------------
Reporter: pobsteta | Owner: martinl
Type: defect | Status: assigned
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Keywords: wxNviz | Platform: MacOSX
Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Comment(by helena):
it works now - if I include grass6 vector data it suggests to rebuild
topology and after rebuilding, I can switch to 3D without trouble. I
think that this can be closed,