Opened 16 years ago
Closed 16 years ago
#282 closed defect (fixed)
r.what in wxGUI should not depend on computational region
| Reported by: | msieczka | Owned by: | martinl |
|---|---|---|---|
| Priority: | major | Milestone: | 6.4.0 |
| Component: | wxGUI | Version: | svn-develbranch6 |
| Keywords: | Cc: | grass-dev@… | |
| CPU: | All | Platform: | All |
Description
r.what in wxGUI should not depend on computational region like it does. Example:
- 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
- Add a raster map to manager.
- Right-click it > Zoom to selected map.
- Query anywhere within the map - r.what always returns NULL, in error.
- Now again in terminal set region to cover the whole map.
- Query again in wxGUI - now it works.
GUI's region and computational region should be separate.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
Should be fixed in r33276.
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
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!