[GRASS5] New release candidate 3 of GIS Manager 2

Michael Barton michael.barton at asu.edu
Wed Feb 15 19:02:56 EST 2006

I don't  know if you can crash an xmonitor by excessively resizing it,
causing the xdriver to redraw repeatedly. Maybe if you work at it...

But the xdriver works differently from the PNG driver I have to use for the
new GIS Manager. I suspect that by resizing excessively in the new GIS
Manager, you end up building up too many pending processes in a buffer
somewhere. I've trapped as much of this as I know how to keep someone from
doing this, but you can apparently manage to get by these if you work at it.

Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ  85287-2402

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

> From: Maciek Sieczka <werchowyna at epf.pl>
> Date: Tue, 14 Feb 2006 21:12:17 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass5 at grass.itc.it>, <GRASSLIST at baylor.edu>
> Subject: Re: [GRASS5] New release candidate 3 of GIS Manager 2
>> Due to the way that GRASS displays work at the moment, if you
>> excessively resize the window, it will eventually bomb.
> Do you mean it should happen as well with gis.m "Map Displays" as with
> old monitors? With old monitors it never happens for me, no matter what
> a saddist I am...
>>> 5.

More information about the grass-dev mailing list