vdigit: don't force 'cat' as the key column name

[msieczka]

r33285

When a new vector map is created in vdigit, it forces 'cat' as the key column name. This is not really bad, and very common in other GRASS modules, but I think it should be possible to specify a custom key column name in any module that creates a vector map with a linked table.

[martinl]

You can change default key column in GUI Preferences ("Attributes" tab).

[msieczka]

Replying to martinl:

You can change default key column in GUI Preferences ("Attributes" tab).

Cool, but that's not the same thing. I mean, that, ideally, the key column setting should be adjustable ad command run time, too (this issue is not limited to vdigit actually).

[martinl]

Replying to msieczka:

Cool, but that's not the same thing. I mean, that, ideally, the key column setting should be adjustable ad command run time, too (this issue is not limited to vdigit actually).

Not only vdigit, also creating vector map layer from main menu ('Vector->Develop vector map->Create new vector map').

Do you mean to use GIS/environment variable like GRASS_KEY_COLUMN ?

[msieczka]

Replying to martinl:

Replying to msieczka:

Cool, but that's not the same thing. I mean, that, ideally, the key column setting should be adjustable ad command run time, too (this issue is not limited to vdigit actually).

Not only vdigit, also creating vector map layer from main menu ('Vector->Develop vector map->Create new vector map').

I know.

Do you mean to use GIS/environment variable like GRASS_KEY_COLUMN ?

Oh, it would be usefull for sure, but that's not exactly what I meant. I meant that each command that creates a vector map with a linked table should allow for specifying the key column name at it's runtime. Having such functionality *and* a global variable for a default, would be optimal.

[martinl]

Replying to msieczka:

Oh, it would be usefull for sure, but that's not exactly what I meant. I meant that each command that creates a vector map with a linked table should allow for specifying the key column name at it's runtime. Having such functionality *and* a global variable for a default, would be optimal.

Try r48512 (trunk) or r48513 (devbr6).

[martinl]

Replying to martinl:

Replying to msieczka:

Oh, it would be usefull for sure, but that's not exactly what I meant. I meant that each command that creates a vector map with a linked table should allow for specifying the key column name at it's runtime. Having such functionality *and* a global variable for a default, would be optimal.

Try r48512 (trunk) or r48513 (devbr6).

Note that it affects only creating new vector maps dialog.