[GRASS-dev] [GRASS GIS] #1978: module GUIs: "or enter values interactively" should be opt-in

GRASS GIS trac at osgeo.org
Fri Jun 21 11:44:58 PDT 2013

#1978: module GUIs: "or enter values interactively" should be opt-in
 Reporter:  hamish  |       Owner:  grass-dev@…              
     Type:  defect  |      Status:  new                      
 Priority:  normal  |   Milestone:  6.4.4                    
Component:  wxGUI   |     Version:  svn-trunk                
 Keywords:  parser  |    Platform:  All                      
      Cpu:  All     |  

Comment(by annakrat):

 Replying to [comment:2 hamish]:
 > If term 2 (element) is "file", trunk's libgis checks to see if the file
 already exists & insists on --overwrite. So for file input= and output=
 term 2 should probably stay as "file".  This also means that the GUI
 should use term 2 (element) to decide if there should be a file [Browse]
 button present, instead of term 3 (prompt/description) as it does now.

 > so that leaves the switch for deciding on a text input box to be based
 on the third term (prompt/description). (as far as
 gui/wxpython/gui_core/forms.py is concerned)
 > so e.g. for r.in.mat we have this info from --interface-description
 >  <gisprompt age="old" element="mat" prompt="file" />
 > `element` would go back to "file", and term 3, `prompt` (aka
 description), would change from "file" to "text" (or "bin" or generic
 > And the "or enter text interactively" box would be made to only show up
 if `prompt` was "text".

 I agree. "file" as element and "text" or "bin" as prompt (this is what you
 mean, is it?). Currently it's the opposite way. Apart from "bin", grep
 shows also "camera" or "font" - is there any reason to keep them?

Ticket URL: <https://trac.osgeo.org/grass/ticket/1978#comment:3>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list