[haiku] Re: Behavior of popup menus

  • From: pete.goodeve@xxxxxxxxxxxx
  • To: haiku@xxxxxxxxxxxxx
  • Date: Tue, 21 Dec 2010 19:05:57 -0800

On Wed, Dec 22, 2010 at 01:45:49AM +0100, Ingo Weinhold wrote:
> 
> Let me rephrase: This is how all menu bars and the context menus in all 
> applications I use under BeOS work. At least with the "Click to Open" 
> preference setting checked (which is the default and which AFAIK doesn't even 
> exist under Haiku).

Ever used ArtPaint...? (:-))  That's one that isn't mine that keeps
its context menus up only while the button is down.  I have to admit
though that most of those I've browsed keep the menu up after a click.

Travis' favourite (:-)) 'Magnify' is of course another one, but that
is *not* a good example -- except of bad Human Factors in general.
(Using a popup menu in that mode is ridiculous.  How can you 'Save'
the image you want when you first have to move the mouse so it's showing
a magnification of the magnification?!)  I also noticed that whether
the menu is sticky or not seems a bit random, perhaps depending on
where exactly in the window you are.

> 
> > The default behaviour (if you use
> > Go() with no options) is for the menu to remain only while the button is
> > down.  (See my earlier extensive post.)  This is what I find most natural,
> > and what I've always coded for.  The patch would *change* the default.
> 
> The patch would just make the API-wise default what appeared to be the 
> behavioral default in all applications (perhaps except yours) in BeOS.

My worry is that it *will* break apps that do slightly non-standard things.
For instance, I typically offset the menu point by 5 pixels, so that it's
clear the cursor is not on it.  When I tried (emulating) the patch with
that condition, the cursor when released is outside the 4x4 clickToOpenRect,
so the menu always goes away without being able to select anything!

> 
> The thing I would change (besides fixing the bugs) is to only keep the menu 
> open, if the click was actually a click (i.e. a quick sequence of mouse down 
> and mouse up). This would make the behavior not get in your way of use and 
> shouldn't affect the usually "click to open" behavior either.

Well, I guess I'm the only one here who likes "pop-up-down" menus, so
it's hard to fight.  [Guess I've been used to them ever since the Amiga
days...]  As long as a menu will always be dismissed if you move the
cursor away from it before releasing, I'll survive!

        -- Pete --


Other related posts: