[GRASS5] column names GUI button

[Michael Barton]

Markus,

This is GREAT. I NEVER remember the column names, as the cerebral hard disk
has long since filled up and I must make due with an antiquated indexing
program ;-)

When will this be functional enough to begin using in c-modules and scripts?

Thanks very much again!

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: Markus Neteler <neteler at itc.it>
> Date: Tue, 17 May 2005 18:06:54 +0200
> To: grass5 developers list <grass5 at grass.itc.it>
> Subject: [GRASS5] column names GUI button
> 
> Hi,
> 
> usually I don't remember the column names of a vector map. For
> this once we added '-c' to v.info to generate the list of column names,
> such as
> 
> v.info -c roads
> Displaying column types/names for database connection of layer 1:
> INTEGER|cat
> CHARACTER|label
> 
> But it would be nice to have this as a button in the GUI.
> So I have added three new functions to VECTLIB:
> 
>  char *Vect_get_column_names (struct Map_info *Map, int field);
>  char *Vect_get_column_types (struct Map_info *Map, int field);
>  char *Vect_get_column_names_types (struct Map_info *Map, int field);
> 
> which generate a comma separated list as (potential) input to a
> GUI button, e.g. in display/d.vect/main.c
> 
>   attrcol_opt->answers    = Vect_get_column_names (&Map, atoi
> (lfield_opt->answer));
> 
> Unfortunately, this code obviously crashes as we neither have Map nor
> lfield_opt
> at this state of program execution (before G_parser()).
> 
> So these new functions are sort of useless (for this task). Anyway, there
> are available now.
> 
> Markus
>