[GRASS5] [bug #3592] (grass) d.vect.thematic: cannot export legend with d.out.png

this bug's URL: http://intevation.de/rt/webrt?serial_num=3592
-------------------------------------------------------------------------

Subject: d.vect.thematic: cannot export legend with d.out.png

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs20050830

When creating a legend with d.vect.thematic, I cannot export this to a file with d.out.png. I have to use a screenshot to do so.

It would be nice to be able to export the legend directly, ideally into a vector file, so that I could then modify it easily in a graphics program.

Maybe there could be an option to export the legend with ps.map instead of displaying it with d.graph...

Moritz

-------------------------------------------- Managed by Request Tracker

this bug's URL: http://intevation.de/rt/webrt?serial_num=3592
---------------------------------------------------------------------

Subject: d.vect.thematic: cannot export legend with d.out.png

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs20050830

When creating a legend with d.vect.thematic, I cannot export this to a
file with d.out.png. I have to use a screenshot to do so.

It would be nice to be able to export the legend directly, ideally
into a vector file, so that I could then modify it easily in a
graphics program.

Maybe there could be an option to export the legend with ps.map
instead of displaying it with d.graph...

To survive d.redraw et al. d.graph input needs to be added to the
command history list via a temporary file. d.text does this already.

Then it will survive the trip through d.out.png.

Hamish

How can d.graph input be added to the command history? Is this something
that needs to be added to the d.graph C module?

Michael
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

From: Hamish <hamish_nospam@yahoo.com>
Date: Sat, 17 Sep 2005 01:40:58 +1200
To: Request Tracker <grass-bugs@intevation.de>
Cc: <grass5@grass.itc.it>
Subject: Re: [GRASS5] [bug #3592] (grass) d.vect.thematic: cannot export
legend with d.out.png

this bug's URL: http://intevation.de/rt/webrt?serial_num=3592
---------------------------------------------------------------------

Subject: d.vect.thematic: cannot export legend with d.out.png

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs20050830

When creating a legend with d.vect.thematic, I cannot export this to a
file with d.out.png. I have to use a screenshot to do so.

It would be nice to be able to export the legend directly, ideally
into a vector file, so that I could then modify it easily in a
graphics program.

Maybe there could be an option to export the legend with ps.map
instead of displaying it with d.graph...

To survive d.redraw et al. d.graph input needs to be added to the
command history list via a temporary file. d.text does this already.

Then it will survive the trip through d.out.png.

Hamish

How can d.graph input be added to the command history?

the input (piped from stdin) is written to a temporary file and the
command history is changed so that the command line references that
input file instead of expecting input from stdin. The .tmp file is
persistent until you quit GRASS at which time it is cleared (possible
problem with server installs, but d.text already does this eg).

Is this something that needs to be added to the d.graph C module?

Yes.

I would like to have wish #3241 done first (merge d.mapgraph into
d.graph) see http://intevation.de/rt/webrt?serial_num=3241

step 1) for that is merge the bugfixes and updates from d.mapgraph into
d.graph (malloc -> G_malloc, ...), otherwise they are essentially the
same exact code. I would prefer a better C programmer than me did this.

step 2) add -m flag to d.graph to indicate input coordinates are map
units, not percentage of frame. I'm happy to do this part.

We should avoid duplicating the effort of modifying both modules for the
same feature or allow one module to go off on a tangent which would make
the merge that much harder in the future.

Hamish

This sounds like a very reasonable plan. When they are merged, it would be
nice if the combined one could also draw a circle as well as a box and line.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

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

From: Hamish <hamish_nospam@yahoo.com>
Date: Mon, 19 Sep 2005 14:14:55 +1200
To: Michael Barton <michael.barton@asu.edu>
Cc: <grass-bugs@intevation.de>, <grass5@grass.itc.it>
Subject: Re: [GRASS5] [bug #3592] (grass) d.vect.thematic: cannot export
legend with d.out.png

How can d.graph input be added to the command history?

the input (piped from stdin) is written to a temporary file and the
command history is changed so that the command line references that
input file instead of expecting input from stdin. The .tmp file is
persistent until you quit GRASS at which time it is cleared (possible
problem with server installs, but d.text already does this eg).

Is this something that needs to be added to the d.graph C module?

Yes.

I would like to have wish #3241 done first (merge d.mapgraph into
d.graph) see http://intevation.de/rt/webrt?serial_num=3241

step 1) for that is merge the bugfixes and updates from d.mapgraph into
d.graph (malloc -> G_malloc, ...), otherwise they are essentially the
same exact code. I would prefer a better C programmer than me did this.

step 2) add -m flag to d.graph to indicate input coordinates are map
units, not percentage of frame. I'm happy to do this part.

We should avoid duplicating the effort of modifying both modules for the
same feature or allow one module to go off on a tangent which would make
the merge that much harder in the future.

Hamish

This sounds like a very reasonable plan. When they are merged, it
would be nice if the combined one could also draw a circle as well as
a box and line.

with a D_symbol() library function d.graph could draw icons too...

Hamish