#1742: WXGUI layer manager window doesn't show all menubar entries
-------------------------+--------------------------------------------------
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone: 7.0.0
Component: wxGUI | Version: svn-releasebranch64
Keywords: menu | Platform: Linux
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Comment(by cmbarton):
Replying to [comment:16 wenzeslaus]:
>
> Hamish wrote on ML ([GRASS-dev] GRASS GIS 7 tech-preview release
preparations):
> > I welcome better presentation of the menus since they get rather big
(platoon rule of thumb: any more than ~12 in any level/group gets a bit
overwhelming), but wrt "search to run" as the primary instead of
augmenting method, I fear that way is not very discoverable -- at least
I'd like to avoid the situation where a new user needs to know the name of
what they're looking for before they can find it, which isn't so good to
explore & learn about new modules you don't know exist yet. Especially for
a software so big as ours which takes years to fully know.
>
> Look at the 'Search modules' in lmgr. There is a search box but also a
tree which you can browse.
>
> > We are spatial creatures, so a spatial model for menu layout where we
can use our spatial & muscle memories helps I think. Our monitors are
getting really wide these days, both desktop and laptop, and so top menu
bars will fit even better than they used to, we just have to make the
windows a bit wider to compensate. Luckily these days there's space for
that. (2c)
>
> Bit wider is not enough for German, it has to be much bigger.
I can make the window MUCH wider if I want and then save it so that it
opens that wide every time I start the GUI afterwards. So I'm not sure I
understand the problem. It seems that the issue is a combination of having
long words for menu headings, small displays, and low resolution. Or do I
misunderstand? If this is the crux of it, I'm not convinced that we should
rework the entire GUI for all other GRASS users in order to deal with that
specific problem.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1742#comment:18>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
