The menu at the bottom is for compatibility with old applications. You should not be relying on it with new applications.
Put an affordance somewhere in your UI to invoke this thing. The menu button is no longer a guaranteed affordance. On Fri, Jul 13, 2012 at 5:32 PM, limtc <[email protected]> wrote: > I am faced with an issue trying to support full screen app (in both an > arcade game and an infant painting program). There will be no ActionBar > when the app run, but I needs to support Android 3.2 for some of the > features I used. > > If there is no ActionBar, the ideal place for the menu will be at the > bottom (status bar?) just like old app running on Android 3/4. I cannot > depend on a dedicated hardware button as many new phones will not have it > anymore. > > So what's the solution in such a case? Thanks! > > -- > 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 -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
