[GRASS5] Re: mapset changing script

[Hamish]

> > Flag for not erasing displays?  I'll often have 20 mapsets within a
> > location specifying individual study sites, each with common map
> > names. I then jump between them & d.redraw to quickly have a look at
> > what is next door.
> 
> The main reason for the need to erase the monitor when switching
> mapsets is that some d.* modules use the current region from the WIND
> file, while others use the region which is stored on the monitor.
> 
> Consequently, it's recommended that you erase the monitor whenever the
> current region changes. And changing the mapset will typically change
> the current region.

Is there anything fundamentally wrong with forcing a "d.redraw" instead
of a "d.erase" action?
 (I'm not really arguing to change it, just curious)

In the past after changing mapsets I've just assumed the monitor to be
wrong until I update it with d.redraw or by tweaking the edge of the
monitor for a slight resize.. never really thought about it.


Hamish