[GRASS5] Re: d.rgb: different display in gis.m and d.m

[Michael Barton]

Maciek,

I *THINK* you've hit a bug I reported in d.rgb and d.his about a month back.
I'm pretty sure that they treat "0" as NULL. This is probably a holdover
from the old 'pre-NULL' days of GRASS. Does your map use "0"s? If so, try
changing to another value and see what happens.

I don't know why it's showing up in gis.m and not in d.m, but probably has
to do with the x11 vs. PNG/PPM display driver architecture. I'm adding Glynn
to the copy list because he may have some insight into what is going on.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Maciek Sieczka <werchowyna at epf.pl>
> Date: Mon, 1 May 2006 13:40:29 +0200
> To: <grass5 at grass.itc.it>
> Cc: <michael.barton at asu.edu>, <cedricgrass at shockfamily.net>,
> <hamish_nospam at yahoo.com>
> Subject: d.rgb: different display in gis.m and d.m
> 
> Hi,
> 
> Please see the attched screendumps. Both are the output of 'd.rgb
> red=d.r green=d.g blue=d.b -o' called from gis.m (rgb_tcltk.png) and
> d.m (rgb_mon.png) respectively. Why is the first one different? The
> latter one (rgb_mon.png) seems correct, as r.composite output is
> identical.
> 
> Maciek
> 
> 
> --------------------
> W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko
> najlepsze z nich!
> http://katalog.panoramainternetu.pl/