android onOptionsMenuClosed not being called for submenu

views:

answers:

+1 Q:

android onOptionsMenuClosed not being called for submenu

I want to be able to automatically unpause my app when the user exits from the options menu. (unless, of course, they have selected pause...)

Handling it onOptionsMenuClosed works fine for the top level menu but is not called for a submenu. The higher level onPanelClosed does not appear to be called either.

I can detect when they enter the menu and if they make a selection but not if they just hit the menu button to exit.

I could rewrite the whole submenu to use a dialog but I'd rather not if it can be avoided.

Does anyone have any suggestions?

You can override onKeyDown and implement a menu yourself when the menu button is detected.

schwiz 2010-09-10 21:19:00

It's certainly an option but it shouldn't really be necessary to circumvent the whole menu system to do this. (And possibly a bit risky since it's clearly not what the designers of Android expect you to do)

FixerMark 2010-09-10 21:36:27

I don't see why not, how else can you have a highly stylized menu? I think its the best way to go especially for a game. You could even start a new activity for result with a transparent darkened background when you detect menu pressed.

schwiz 2010-09-10 21:48:49

Note that you can exit the menu just by tapping anywhere on the screen, you don't necessarily have to hit the menu button again, so this won't work for all cases.

Mayra 2010-09-10 21:52:51

Mayra you would have to handle that logic yourself. If you do it with an activity overlay method that I mentioned in the comment above you would just call finish when menu is pressed in that activity.

schwiz 2010-09-10 22:05:52

Ok, but 9 times out of 10, implementing your own menu is the wrong way to go. If you have some highly stylized app like a game it might be ok, but generally Android users expect the menu button to behave a specific way, and you will just confuse them if you do something different.

Mayra 2010-09-10 22:43:46

Thanks for the suggestions. I may have to look into implementing the menu as an overlay activity.

FixerMark 2010-09-11 17:59:50

+1 A:

You could override the onkeydown , set a flag to check if the menu is shown or not do you thing then return super.onKeyDown(keyCode, event); .

You could check if menu if on screen on every keydown.Keep in mind that other buttons (Back , search and home and touch on other part of the screen closes the menu.) .With other buttons you may do handle them but home botton and finger tap cannot be override.

If i was you i whould forget the @override on onkeydown option for that purpose

But you can have 6 menu buttons the 6th called "More" and that could create a custom dialog with more options that you can handle

weakwire 2010-09-10 21:43:22

ansaurus

tags:

views:

answers:

android onOptionsMenuClosed not being called for submenu

related questions