Opened 11 years ago

Closed 8 years ago

#287 closed defect (fixed)

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

Reported by: msieczka Owned by: martinl
Priority: minor Milestone: 6.4.3
Component: Default Version: svn-develbranch6
Keywords: Cc: grass-dev@…
CPU: All Platform: All

Description

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.

Change History (8)

comment:1 Changed 11 years ago by martinl

Cc: grass-dev@… added
Owner: changed from grass-dev@… to martinl
Status: newassigned

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

comment:2 in reply to:  1 ; Changed 11 years ago by msieczka

Component: wxGUIdefault

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).

comment:3 in reply to:  2 ; Changed 11 years ago by 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 ?

comment:4 in reply to:  3 ; Changed 11 years ago by 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.

comment:5 in reply to:  4 ; Changed 8 years ago by 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).

comment:6 Changed 8 years ago by martinl

Milestone: 6.4.06.4.3

comment:7 in reply to:  5 Changed 8 years ago by 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.

comment:8 Changed 8 years ago by martinl

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.