When using OneClickMenu configuration option, clicking anywhere in the menu bar activates menu selection even if a menu label/icon wasn't clicked

[morgant]

In troubleshooting some issues with custom applications "swallowed" into the mlvwm menu bar, I've discovered that -- if one is using the OneClickMenu configuration option which keeps menus open until a second click -- clicking anywhere in the menu bar activates the menu selection, even if the initial click was not on a menu label/icon. Most applications swallowed into the menu bar are just for display/informational purposes (e.g. xload, xmem, mlclock, etc.) so this is a non-issue, but I'm starting to add/implement more clickable applications, including some that implement their own menus (e.g. xsndiomenu). In this case, the first click on the application in the menu bar can be caught by mlvwm's menu handling, requiring a second click to complete the menu handling and then get passed to the swallowed application.

[morgant]

My initial triaging hints at this being handled in menus.c's press_menu(), which is called from event.c's handle_button_press(), though this will need to be confirmed.