[GRASS-dev] [GRASS GIS] #2766: GUI not able to create dropdown lists of columns for more than one map or table (was: it is not possible to set other column when working with v.db.join from gui)

GRASS GIS trac at osgeo.org
Wed May 11 02:22:48 PDT 2016


#2766: GUI not able to create dropdown lists of columns for more than one map or
table
----------------------------+--------------------------
  Reporter:  lfurtkevicova  |      Owner:  grass-dev@…
      Type:  defect         |     Status:  new
  Priority:  normal         |  Milestone:  7.2.0
 Component:  wxGUI          |    Version:  7.0.1
Resolution:                 |   Keywords:  column lists
       CPU:  x86-64         |   Platform:  Linux
----------------------------+--------------------------
Changes (by mlennert):

 * keywords:   => column lists
 * priority:  blocker => normal
 * component:  Database => wxGUI


Comment:

 Replying to [ticket:2766 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

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2766#comment:2>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list