Can the color table names/descriptions be added to v.colors, like they are for r.colors so that a color table pull-down will be automatically generated in the TclTk and wxPython gui's?
Thanks
Michael
Can the color table names/descriptions be added to v.colors, like they are for r.colors so that a color table pull-down will be automatically generated in the TclTk and wxPython gui's?
Thanks
Michael
On Wed, Dec 31, 2008 at 4:41 AM, Michael Barton <michael.barton@asu.edu> wrote:
Can the color table names/descriptions be added to v.colors, like they are
for r.colors so that a color table pull-down will be automatically generated
in the TclTk and wxPython gui's?
Since v.colors is a script, AFAIK it is not possible.
Markus
On Dec 31, 2008, at 5:35 AM, Markus Neteler wrote:
On Wed, Dec 31, 2008 at 4:41 AM, Michael Barton <michael.barton@asu.edu> wrote:
Can the color table names/descriptions be added to v.colors, like they are
for r.colors so that a color table pull-down will be automatically generated
in the TclTk and wxPython gui's?Since v.colors is a script, AFAIK it is not possible.
Actually, it's quite possible. Since it's a script, I can make the change.
Michael
Fixed in all versions.
Michael
____________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>
On Dec 31, 2008, at 5:35 AM, Markus Neteler wrote:
On Wed, Dec 31, 2008 at 4:41 AM, Michael Barton <michael.barton@asu.edu> wrote:
Can the color table names/descriptions be added to v.colors, like they are
for r.colors so that a color table pull-down will be automatically generated
in the TclTk and wxPython gui's?Since v.colors is a script, AFAIK it is not possible.
Markus
Hi,
2008/12/31 Michael Barton <michael.barton@asu.edu>:
Fixed in all versions.
well, r.colours options are generated on the fly (from
$GISBASE/etc/colours). Actually it's not possible for v.colours as
Markus wrote. Color table options in v.colours are static and must be
updated everytime $GISBASE/etc/colours is changed.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
On Dec 31, 2008, at 3:57 PM, Martin Landa wrote:
Hi,
2008/12/31 Michael Barton <michael.barton@asu.edu>:
Fixed in all versions.
well, r.colours options are generated on the fly (from
$GISBASE/etc/colours). Actually it's not possible for v.colours as
Markus wrote. Color table options in v.colours are static and must be
updated everytime $GISBASE/etc/colours is changed.
That's the down side of doing this as a script. On the other hand, the color tables are not changed all that often, and it is hard to know what you can type without the pull-down options combo. IMHO, entering a static list is a lot better for a GUI than not having any list at all. If you want a new table that is not yet in the static list, it is still possible to run v.colors from the command line.
Michael
On Wed, Dec 31, 2008 at 10:45 PM, Michael Barton <michael.barton@asu.edu> wrote:
On Dec 31, 2008, at 5:35 AM, Markus Neteler wrote:
On Wed, Dec 31, 2008 at 4:41 AM, Michael Barton <michael.barton@asu.edu>
wrote:Can the color table names/descriptions be added to v.colors, like they
are
for r.colors so that a color table pull-down will be automatically
generated
in the TclTk and wxPython gui's?Since v.colors is a script, AFAIK it is not possible.
Actually, it's quite possible. Since it's a script, I can make the change.
Sure but now it is hardcoded. If in libgis a change is done, the
developer needs to remember to update v.colors as well
(in GRASS >= 6.4 the color stuff was centralised in libgis to not
have it scattered around).
I don't know about v.colors.py in GRASS 7, I hope that the
C function can be called there which generates the color table
list.
Markus
Hi,
2009/1/1 Markus Neteler <neteler@osgeo.org>:
I don't know about v.colors.py in GRASS 7, I hope that the
C function can be called there which generates the color table
list.
I think in GRASS7 v.colors should be replaced with something more
sophisticated. Coloring vector features based on attribute column or
optionally based on color table, e.g. via d.vect.
d.vect rgbcolumn or colortable
?
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
Have you seen the new color rules interface for wxPython that I added some months ago? A color table option could be added to this.
Michael
On Jan 1, 2009, at 9:34 AM, Martin Landa wrote:
Hi,
2009/1/1 Markus Neteler <neteler@osgeo.org>:
I don't know about v.colors.py in GRASS 7, I hope that the
C function can be called there which generates the color table
list.I think in GRASS7 v.colors should be replaced with something more
sophisticated. Coloring vector features based on attribute column or
optionally based on color table, e.g. via d.vect.d.vect rgbcolumn or colortable
?
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *