Re: AppMenu design feedback

[Adam Tauno Williams <awilliam whitemice org>]

On Fri, 2013-02-22 at 20:37 +0000, Sam Bull wrote:
> On Fri, 2013-02-22 at 12:06 +0000, Gabriel Rossetti wrote:
> > I find the AppMenu counter-productive, confusing (why have menus in
> > two different places?) and it breaks the sloppy mouse focus (you can't
> > access the AppMenu since it changes when the mouse goes over another
> > window when you try and access it).
> In 3.6, sloppy focus has a short delay, so if you flick the cursor to
> the top of the screen, it won't change focus and the menu works just
> fine.

Yep.  It isn't even really a 'flick', the delay is long enough for me to
easily traverse the 36inches across my display.  I haven't had it *not*
work.

> The AppMenu seems like a nice idea to remove the menu bar from
> applications that only use it for a couple of trivial menu items (like
> preferences and quit).

Agree.  And <super>F10 will take you there without mouse motion.

> But, it can be confusing when an application actually chooses to split
> menu items between the two places (e.g. Devhelp). I think applications
> should choose one option or the other, and never use both menus.

I pretty much agree;  I suppose there are some reasonable exceptions out
there somewhere, seems like there always is.  But what you say seems
like a very good guideline.

> I don't think it's confusing if only one is used. If there is no menu
> bar on the application, then it is obvious that any additional options
> will be on the AppMenu.


-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA