#282: r.what in wxGUI should not depend on computational region
----------------------+-----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: wxGUI | Version: svn-develbranch6
Keywords: | Platform: All
Cpu: All |
----------------------+-----------------------------------------------------
r.what in wxGUI should not depend on computational region like it does.
Example:
1. In GRASS terminal set your region to something outside the raster map
you are going to query, e.g.:
{{{
g.region n=2 e=2 w=1 s=1 res=1 -a
}}}
2. Add a raster map to manager.
2. Right-click it > Zoom to selected map.
3. Query anywhere within the map - r.what always returns NULL, in error.
4. Now again in terminal set region to cover the whole map.
5. Query again in wxGUI - now it works.
GUI's region and computational region should be separate.
#282: r.what in wxGUI should not depend on computational region
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: wxGUI | Version: svn-develbranch6
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by hamish):
The GUI can set the GRASS_REGION or WIND_OVERRIDE enviro variables prior
to running to locally/temporarily change the region.
see the variables.html help page for usage, and/or lib/gis/get_window.c
unless WIND_OVERRIDE already exists, GRASS_REGION might be the one to use
here.
Hamish
ps- thanks to you both for working through this flood of wxgui bug
reports. It can be really frustrating dealing with them all but the result
will be a much more solid and usable GUI upon release. kudos!