Opened 4 years ago

Last modified 15 months ago

#2766 new defect

GUI not able to create dropdown lists of columns for more than one map or table

Reported by: lfurtkevicova Owned by: grass-dev@…
Priority: normal Milestone: 7.2.4
Component: wxGUI Version: 7.0.1
Keywords: column lists Cc:
CPU: x86-64 Platform: Linux

Description

Problem with joinig database table to a vector map table using v.db.join from gui: parameters map, column and other_table are OK, but it isn't possible to set other_column

Change History (9)

comment:1 Changed 4 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:2 in reply to:  description ; Changed 4 years ago by mlennert

Component: DatabasewxGUI
Keywords: column lists added
Priority: blockernormal
Summary: it is not possible to set other column when working with v.db.join from guiGUI not able to create dropdown lists of columns for more than one map or table

Replying to lfurtkevicova:

Problem with joinig database table to a vector map table using v.db.join from gui: parameters map, column and other_table are OK, but it isn't possible to set other_column

This is a more general problem than only in v.db.join (see column and to_column in v.distance or points_column option in v.vect.stats for example): whenever you need to specify columns in two different maps, the GUI cannot handle this. Only the columns of one map are in the list. I'm no expert in the GUI, but I imagine the G_OPT_DB_COLUMN standard parser option looks for columns in the map defined by G_OPT_V_MAP or G_OPT_V_INPUT, but it can only handle one defined in this way.

This needs some fundamental solution in the wxgui, not a specific module.

In any case, the does not render the module unusable, even in the GUI, as one can always type the column name.

So, I'm downgrading this to normal and changing the title of the bug.

Moritz

comment:3 in reply to:  2 Changed 4 years ago by mlennert

Replying to mlennert:

Replying to lfurtkevicova:

Problem with joinig database table to a vector map table using v.db.join from gui: parameters map, column and other_table are OK, but it isn't possible to set other_column

This is a more general problem than only in v.db.join (see column and to_column in v.distance or points_column option in v.vect.stats for example): whenever you need to specify columns in two different maps, the GUI cannot handle this. Only the columns of one map are in the list. I'm no expert in the GUI, but I imagine the G_OPT_DB_COLUMN standard parser option looks for columns in the map defined by G_OPT_V_MAP or G_OPT_V_INPUT, but it can only handle one defined in this way.

This needs some fundamental solution in the wxgui, not a specific module.

IIUC the code, the issue is in the UpdateThread? class in gui/wxpython/gui_core/forms.py, where only one map is handled. But I don't have enough expertise of that code to go much further.

comment:4 Changed 3 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:5 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:6 Changed 2 years ago by neteler

Milestone: 7.2.27.2.3

Ticket retargeted after milestone closed

comment:7 Changed 20 months ago by martinl

Milestone: 7.2.3

Ticket retargeted after milestone closed

comment:8 Changed 20 months ago by martinl

Milestone: 7.2.4

comment:9 Changed 15 months ago by pvanbosgeo

Just was bitten by this issue. Just as a further specification, this is not only a problem if one wants to specify columns in two different maps, but also when one wants to select two columns (as two separate variables) from the same map.

Note: See TracTickets for help on using tickets.