Dear Paul and Glynn: thank you very much for your feedback.
Glynn Clements wrote:
[...]
The problem with using monitors on native Windows isn't the graphics,
it's the client-server communication.
OK: hopefully I won't bother the list any longer on X-monitors.
[...]
If the environment variable GRASS_RENDER_IMMEDIATE is set to TRUE, PNG
or PS, all d.* commands write graphics directly to a file, without
using a monitor.
The filename, format and dimensions are set by environment variables,
as described at:
http://grass.ibiblio.org/gdp/html_grass63/variables.html#png
http://grass.ibiblio.org/gdp/html_grass63/variables.html#ps
All of the functionality of the PNG and PS drivers is available in
this way.
This works fine in my Cygwin/grass6.2.2 installation, although the
GRASS_PNG_READ variable does not seem to be available in grass6.2
http://grass.ibiblio.org/gdp/html_grass62/pngdriver.html so the overlay
thing suggested by Paul wouldn't work.
Trying the same with native winGRSSS 6.3.0 RC5 is less of a success: (1)
no way to set environment variables via the GUI Output - GIS.m window;
(2) not able to start GRASS via cmd.exe as suggested at
http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status
by typing the following at the cmd.exe prompt:
C:\grass63RC5\bin\grass63.bat -text
I get the output below:
Welcome to GRASS 6.3.0RC5 (2008)
GRASS homepage: http://grass.itc.it/
This version running thru: Windows Command Shell (cmd.exe)
When ready to quit enter: exit
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
"cmd.exe" non รจ riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
(the Italian error message would sound more or less like: "cmd.exe" is
not recognized as an internal or external command, an executable program
or a batch file.)
Thanks again for your time and insights,
Luigi
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
