[GRASS-dev] [GRASS GIS] #2042: wxgui: no more menu access to r.in.gdal / v.in.ogr
GRASS GIS
trac at osgeo.org
Fri Aug 2 19:28:55 PDT 2013
#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 hamish):
As long at the button is worded correctly and put in an appropriate place,
it doesn't have to be confusing. Putting it along side as a menu item
might be confusing for sure. Typing 'r.in.gdal --ui' (//are you saying
that just 'r.in.gdal' will not cause the module GUI to open?) from a
command prompt requires prior knowledge of the module's name and knowing
how to do that. Neither is inherently "discoverable" or self-documenting.
The --ui trick is hardly widely known outside of the development team.
see also the cartographic composer's way of launching the ps.map dialog
from the File menu. It's there if you want/need it, but not likely to
confuse new users.
> Similarly for the other modules which have special frontend, e.g.
> i.group. From my personal experience, the user in the class were
> very confused when they got different GUI dialog when running
> i.group from the menu and command prompt.
I would suggest the solution there is different wording titlebar etc text
in the wizard version. i.e. give them better hints along the way to guide
their expectations. (easier said than done of course)
regards,
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2042#comment:5>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list