| 1 | | We should give users a chance to abort or correct their action by moving the mouse somewhere else and releasing it there. So, basically, when in sticky mode, menus should switch to non-sticky mode on MouseDown. I'm not sure how to implement it (I don't know the code well enough), so I hope that someone else knows. :) |
| | 1 | When you are in non-sticky mode (i.e.: hold down mouse button and browse through menu) and move the mouse pointer outside the menu window and then back over the window menu releasing the mouse button doesn't have any effect. It behaves like in sticky mode. Also, if you move the mouse over the parent menu bar after this happened the menu disappears. I can reproduce both every time. |
| | 2 | |
| | 3 | This also sometimes happens when you stay within the menu window all the time. |
| | 4 | |
| | 5 | Sometimes it also closes the menu a short period afterwards (without invoking anything), but when I move the mouse pointer over the menu bar it quickly opens and closes the menu, again. Sometimes it's the other way around. |
| | 6 | |
| | 7 | In rare cases when I hold the mouse button down and switch between menus in a BMenuBar the menu disappears for no reason. |
| | 8 | |
| | 9 | In sticky mode, click and hold mouse button and move the pointer out of the window. The menu will disappear. This only happens when the menu belongs to a BMenuBar. |
