Opened 6 years ago

Closed 6 years ago

#2533 closed defect (fixed)

module GUIs: selected group not taken into account in created command line

Reported by: mlennert Owned by: grass-dev@…
Priority: critical Milestone: 7.0.0
Component: Default Version: svn-releasebranch70
Keywords: group input Cc:
CPU: Unspecified Platform: Unspecified

Description

Using a freshly checked-out and compiled grass7release branch today, I stumbled across the following problem:

  • create a group (and possibly subgroup)
  • open a module that requires a group as input (ex: i.gensig, i.maxlik, i.segment)
  • select a group
  • check the command line at the bottom of the module GUI: you still see group=<required> instead of the group=NameOfSelectedGroup?

This happens which ever way I start the GUI (wxGUI menu, command line, etc). I have not found a way to make the module actually run, since the group entry is required. The only way is to type out everything at the command line (or the command console).

I have seen this behaviour on Debian Testing and Linux Mint LMDE.

Can anybody confirm this ? It is a quite severe bug that makes the GUIs of several modules unusable. Could it be linked to the recent changes in parameter names ?

Attachments (1)

i_gensig_group_selection_bug.png (39.9 KB) - added by mlennert 6 years ago.
example of issue with i.gensig

Download all attachments as: .zip

Change History (4)

Changed 6 years ago by mlennert

example of issue with i.gensig

comment:1 Changed 6 years ago by annakrat

Could you try r63967 in trunk? It is related to the differences between wxPython 2.8 and 3.

comment:2 in reply to:  1 ; Changed 6 years ago by mlennert

Replying to annakrat:

Could you try r63967 in trunk? It is related to the differences between wxPython 2.8 and 3.

Yes, this solves the problem for me. Thanks for the quick fix !

Leaving ticket open for others to test (on Win and Mac OSX ?) and for backport to releasebranch.

Moritz

comment:3 in reply to:  2 Changed 6 years ago by annakrat

Resolution: fixed
Status: newclosed

Replying to mlennert:

Replying to annakrat:

Could you try r63967 in trunk? It is related to the differences between wxPython 2.8 and 3.

Yes, this solves the problem for me. Thanks for the quick fix !

Leaving ticket open for others to test (on Win and Mac OSX ?) and for backport to releasebranch.

Tested at least on Windows. I backported it in r64008.

Note: See TracTickets for help on using tickets.