[GRASS-user] Region definition in Grass 6.1 (and 6.1 cvs)

[Glynn Clements]

Hamish wrote:

> > That calls for an unnecessary intermediate translation. How about
> > "WIND region" for WIND region and "GUI region" for GUI region? ;)
> 
> 
> good point.
> 
> but I wonder if others reading the list know what "WIND" means? and if
> GRASS_REGION or WIND_OVERRIDE enviro variables are set, then WIND region
> is something different than the computational region.

See my previous mail; we shouldn't be talking about WIND at all. The
GUI should use WIND_OVERRIDE and/or GRASS_REGION for everything. The
real issue is the relationship(s) (or lack thereof) between the
regions used for generating the displays and those used for
non-display commands.

The only parts of the GUI which should use WIND are specific commands
whose sole purpose is to synchronise internal GUI regions with the
WIND file, in case the user is using both the GUI and the command
line.

A related issue: it's debatable whether g.region should even be
available from the normal command menu. If it is, the code which runs
commands needs to figure out how to handle the situation where the
command changes the region.

Also related: even if the GUI uses GRASS_REGION, it should still set
WIND_OVERRIDE. $GRASS_REGION only affects reading the region, while
$WIND_OVERRIDE affects both reading and writing. If you set both,
reads will use $GRASS_REGION while writes will use $WIND_OVERRIDE.

-- 
Glynn Clements <glynn at gclements.plus.com>