New information: I just realized that I am unable to demonstrate this behavior on anything other than the Eclipse simulator. That's because I don't have any real Android devices that are both Android 3.0 or above and have a separate hardware menu button. The more modern ways of getting at the menu function (long press the app switcher button, or tap ActionBar overflow icon) all hide themselves when there is no menu to display. But I constructed an Android virtual device in Eclipse by specifying both Android 3.2 and the hardware menu button. So maybe this is a non-problem. I don't have to worry about Android <3.0 because my app requires 3.0 for other reasons. As long as there are no Android devices with both 3.0 and above and a hardware menu key, I think I am OK.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
