[GRASS-dev] [GRASS GIS] #2203: wxGUI module dialogs should provide "reset to default value" for each of parameters

GRASS GIS trac at osgeo.org
Thu Mar 3 04:14:16 PST 2016


#2203: wxGUI module dialogs should provide "reset to default value" for each of
parameters
--------------------------+-------------------------
  Reporter:  marisn       |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.0.0
 Component:  wxGUI        |    Version:  unspecified
Resolution:               |   Keywords:
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by mlennert):

 Replying to [comment:1 annakrat]:
 > Replying to [ticket:2203 marisn]:
 > > Some of autogenerated module dialog input options contain their
 default value. Current implementation has two downsides:
 > >  * there is no way how to get back "default" value if it has been
 changed (a wish for a new feature)
 > >  * once value has been changed, it gets added to the command
 parameters list (nice). The problem - if it's a number field (represented
 by a spiner control), there is no way how to remove it from the module
 parameter list (a bug)
 > >
 > > Potential solution:
 > > Autogenerate a button for each of input fields "reset to default". If
 default value is not specified, it should just clear the input field. If
 the default value is provided, it should just reset to default value. In
 both of cases it should remove parameter from module parameter list.
 >
 > In my opinion, the dialog would be too cluttered with all these buttons
 and we can't use for example context menu because we want to keep the
 system context menu. There could be one button to reset all fields but
 this probably doesn't make any sense.

 I've very little knowledge of wx and am just brainstorming here, but I see
 that spin.ctrl has an option 'initial='. Couldn't this be set to some
 specific value (e.g. -1) and the parser interpret this value to mean that
 this parameter should be ignored ?

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



More information about the grass-dev mailing list