Problem is, this breaks (or doesn't work) if you don't have FULLSCREEN. So all teh comments on "immersive" experience and hiding the actionbar are bollocks. Doesn't "work" even without fullscreen.
The issue here is the HARDWARE menu button that used to be a required button on devices, now Google/Android Team says it isn't. So, the "solution" from Google is "Just use the ActionBar". This doesn't work for some UI's. Sorry, that's the real world folks. UI's can't just "add an actionbar and use the UI". A simple solution is *exactly* what Royston and many others would do. Call openOptionsMenu programmatically from where WE determine it makes most sense with OUR UI, when a HARDWARE "menu/settings" button does not exist on the device. Again and again though with Android, a simple ONE or TWO line code change FAILS and becomes this clusterfuck of problems, attitudes by android devs and other hacks just to get a simple options menu to work across devices. Yes, the Android team has a hard problem, but then again, so does the iOS team, and they are doing a fantastic job. -- 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
