[GRASS-dev] [GRASS GIS] #2042: wxgui: no more menu access to r.in.gdal / v.in.ogr

[GRASS GIS]

#2042: wxgui: no more menu access to r.in.gdal / v.in.ogr
--------------------------------------+-------------------------------------
 Reporter:  mlennert                  |       Owner:  grass-dev@…              
     Type:  defect                    |      Status:  new                      
 Priority:  normal                    |   Milestone:  7.0.0                    
Component:  wxGUI                     |     Version:  svn-trunk                
 Keywords:  r.in.gdal, v.in.ogr, gui  |    Platform:  Unspecified              
      Cpu:  Unspecified               |  
--------------------------------------+-------------------------------------

Comment(by martinl):

 Replying to [comment:6 hamish]:
 > Replying to [comment:4 martinl]:
 > > Moreover running `r.in.gdal` from wxGUI command line should also
 launch GUI
 > > front-end. The autogenerated dialog should appear only when `--ui`
 switch is used.
 >
 > Oh, I understand what you are saying now. And very much disagree -- if a
 user runs 'r.in.gdal' they should get the real r.in.gdal. They are not
 going to type/guess that name by mistake. If the GUI-wizard version is
 presenting itself by that name, then the trouble is there.

 HUH, it was the main issue where the students in my class have problems
 every year. Users can hardly understand that they get *different* dialog
 from the menu and wxGUI command line. Bear in mind, that I speak about
 wxGUI command line and not the terminal!

 > Or do it like 'g.mapsets -s' to launch the extra GUI. (I don't think
 that's a wonderful solution either, but..)

 This kind of switches doesn't make sense to me. Moreover I would do the
 step forward. Launch front-ends from terminal too (when no parameter is
 given), `--ui` would force autogenerated dialog similarly to wxGUI command
 console.

 Let's try to do steps towards the user. Everyone of us has his/her
 specific way of working.

 Martin

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