You could do a few things. Maybe the simplest would be to set a key listener to the menu key, and have it run whatever code you want to go to settings. You could also override onCreateOptionsMenu (called only once) or onPrepareOptionsMenu (called each time menu is displayed). I would think the key listener would be the most direct.
I personally wouldn't do that, if the user expects a menu they should get a menu. But I'm not qualified to talk about what constitutes good Android design. had to override onCreateOptionsMenu to On Oct 19, 12:47 pm, joelt <[email protected]> wrote: > I'm thinking it would be handier if my in my app, a press on the menu > button went straight to my preferences page. I currently have in my > menu two choices: "settings" and "about". About will almost never be > used. I was thinking of putting it in preferences and simply have a > menu button press go straight to preferences. > > Is that considered bad Android design? If not, how would I accomplish > it? > > Joel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
