Opened 10 years ago

Closed 4 years ago

#3908 closed bug (fixed)

Too easy to accidentally select first item off a popup menu

Reported by: jonas.kirilla Owned by: axeld
Priority: normal Milestone: R1
Component: Kits/Interface Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

E.g. in Tracker its easier in Haiku than in BeOS to accidentally select the first item off a popup menu, possibly since the first menu item starts directly at the upper menu border. In BeOS menus there is a thin stripe before the first menu item starts.

Compare right-clicking your desktop 10 times in BeOS and in Haiku. In BeOS the menu usually comes up with no menu item selected, whereas in Haiku it usually comes up with the first menu item selected.

In Haiku I find myself often accidentally selecting the first menu item in Tracker´s context menus. Perhaps I move the mouse too soon after having released the right mouse button (when opening the menu), and the mouse button release message gets wrongly interpreted as being from the new location?

Change History (6)

comment:1 in reply to:  description Changed 10 years ago by idefix

Replying to jonas.kirilla:

In Haiku I find myself often accidentally selecting the first menu item in Tracker´s context menus. Perhaps I move the mouse too soon after having released the right mouse button (when opening the menu), and the mouse button release message gets wrongly interpreted as being from the new location?

This could be related to bug #3267 and #3373.

comment:2 Changed 9 years ago by luroh

Version: R1/pre-alpha1R1/Development

A (temporary?) fix was added in hrev36762. It doesn't cover the issue of right-clicking the handles of replicants though.

comment:3 Changed 9 years ago by saivert

This can be fixed by ignoring the subsequent mouse button up message after the context menu has been shown. Only the clicks after that will trigger the menu item. No need to reposition the menu or add a border to it. Just fix the mouse input handler code.

Wonder why this wasn't part of the design from the beginning. makes sense to me.

comment:4 Changed 9 years ago by anevilyak

That would potentially be problematic if you want to support being able to hold down the mouse button, drag to your desired item and releasing the mouse button to invoke that one (which we currently do).

comment:5 Changed 9 years ago by saivert

yes but you could check for a drag state. when you initiate a drag'n'drop action a flag is set which thus changes the menu input handler logic.

this can be fixed. don't worry!

comment:6 Changed 4 years ago by pulkomandy

Resolution: fixed
Status: newclosed

It was fixed in hrev40306. If the mouse is released before the double-click time, the menu stays open. If it was held longer than that, the menu closes.

Note: See TracTickets for help on using tickets.