On 24/01/08 16:07, Michael Barton wrote:
On Jan 24, 2008, at 2:54 AM, [EMAIL PROTECTED] wrote:
Date: Thu, 24 Jan 2008 10:53:51 +0000
From: Glynn Clements <[EMAIL PROTECTED]>
Subject: Re: [GRASS-dev] why d.vect.thematic won't run on WinGRASS -
d.mon problem
To: Michael Barton <[EMAIL PROTECTED]>
Cc: GRASS developers list <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Michael Barton wrote:
If you just want d.vect.thematic to work with WinGRASS, changing it to
use GRASS_RENDER_IMMEDIATE=TRUE instead of "d.mon start=PNG" would
probably be less work than getting monitors working.
In fact, we recently had to change d.vect.thematic to set
GRASS_RENDER_IMMEDIATE=FALSE so that it's multiple iterations of
d.vect would composite in the PNG monitor and then be output as a PNG
to the GUI.
You can use GRASS_PNG_READ=TRUE to have it read an existing file at
startup, rather than starting with a blank "screen". That way, each
command will overlay the output from previous commands.
--Glynn Clements <[EMAIL PROTECTED]>
Glynn,
This sounds like it might be a way out of this dilemma. Can you explain
this setting a it more? Also, once all the commands are overlayed is
there someway to get them to output to a PNG or PNM so that the GUI can
pick it up--since we can't do it with d.mon stop=PNG?
GRASS_RENDER_IMMEDIATE=TRUE always outputs a PNG or PNM file (depending
on the setting of GRASS_PNGFILE. As the manual on the PNG env variables
says: if you set GRASS_PNG_READ to "TRUE", "the PNG driver will
initialize the image from the contents of $GRASS_PNGFILE", i.e. it will
read the contents of $GRASS_PNGFILE and adds the results of your drawing
command to it. The output thus still is $GRASS_PNGFILE.
Moritz
Michael
____________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
