[GRASS5] XDRIVER pad list and d.rast

[Andreas Lange]

Hi Markus, Hi Eric,

"Eric G. Miller" wrote:
> 
> On Sat, 12 Jan 2002 22:52:47 +0100, Markus Neteler <neteler at itc.it> wrote:
> 
> > Hi,
> >
> > after working in a GRASS session for some more time without
> > d.erase I realized by resizing the monitor, that some
> > 20 display commands had been accumulated (generally fine!).
> >
> > My question/suggestion is: If
> > d.rast map
> > is used, can't this be used to erase the command list in GRASS
> > monitor? As d.rast will overwrite everything (am I wrong?) it's
> > effectively the same as
> > d.erase
> > d.rast map
> 
> Have you never used d.rast to display more than one adjacent or
> overlapping raster?  I think the answer to that question will
> answer your question ;-)
> 

The behaviour of d.rast was as Markus outlined above (calls
D_clear_window if no -o option). 
But i believe that this is not consistent, as no other display module
wipes out the display. And i had problems with the window re-creation
and d.save, because the pad structure was erased with this original
setup. 
And the manual page says:
If the active graphics frame already contains text or graphics, and the
user does not wish to use the -o option, it is wise to first invoke
d.erase to clear the active graphics frame before running d.rast.

So i think the existing users of GRASS have to learn the new setup, and
the new users will enjoy enhanced consistency. Just remember to run
d.frame -e and/or d.erase to initialize the display.

But if you all disagree, i will revert my changes in
src/display/d.rast/cmd/display.c .

Andreas
-- 
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
url: http://mitglied.tripod.de/AndreasLange
mail: Andreas.Lange_at_Rhein-Main.de - A.C.Lange_at_GMX.net