[GRASSLIST:7805] Re: d.legend not showing up in d.out.png

Hamish hamish_nospam at yahoo.com
Sat Aug 6 04:23:22 EDT 2005

> I have noticed in the last couple versions of GRASS 6.0 and 6.1 for 
> linux and macos I have had problems saving the entire contents of a 
> monitor with d.out.png. Specifically, a legend created with d.legend 
> is not included in the output png file... however, everything else is

> there.
> does anyone know why this is happening?

greetings from afar,

modules need to explicitly save their command line to the monitor
history list. (see d.save)

d.legend is only saved to the command list if the at= option is used.
If you use the mouse to do it, it isn't saved.

d.barscale, eg, figures out what the at= settings should be if you use
the mouse and saves that to the command history. d.legend has a lot
more options than d.barscale does so using the same method was messy
and I didn't implement it. I suppose one could do some low level C
string parsing to get it to work but it wasn't a priority during
development as it slows testing.

d.out.png uses d.save to read the command history that it needs to feed
to the PNG driver (d.mon start=PNG).

gripe with the PNG driver: it doesn't respect d.font.freetype settings.

hope that helps,

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

More information about the grass-user mailing list