Concerning the boundaries rendering too thick; under GUI settings (menu:
settings - preferences) under the tab 'Map display', you can set the
Display driver from Cairo (the default I think) to png. That will bring you
back to thinner lines.
I was going to answer that there was an option to
Paulo - PNG display change works a treat!
I'll file a bug report on the interface issue.
Cheers,
Richard
On 19/10/12 6:25 PM, Paulo van Breugel wrote:
Concerning the boundaries rendering too thick; under GUI settings
(menu: settings - preferences) under the tab 'Map display', you can
set the
Hi,
Second, Python selection panels, for modules that should allow multiple
selections, work badly.
well, try eg. `r.report` (which really defines multiple params).
For example, g.copy. In the TCL-TK interface, I can use g.copy for multiple
copies. OK, I usually use the command-line
Dear List,
I am trying to create a hillshade map with shadowing effect of the
topography. It seems r.sunmask should be my weapon of choice, but it is
incredibly slow. Then I found a mail to the userlist in 2007 where
Markus replies on this
Hi there.
I'm trying to do dome tricks with r.colors.stddev and was wondering if
there is a way to know which RGB value will be assigned to a raster value?
More precisely, I want to use the r.colors.stddev scheme in a
moving-window, so that the central pixel is colored
using r.colors.stddev but
On the previous version of Standalone WinGRASS, when installing I
always got a icon on my desktop that allowed me to start grass inside
Msys, so I was able to run scripts by copy and pasting several command
lines directly on
Msys console.
But I noticed that on the recent versions of Standalone
