On Sat, Oct 1, 2011 at 8:12 AM, Zsolt Vasvari <[email protected]> wrote:
> > Having said that however, it will also say that using hardware buttons is > > likely to give a more pleasant user experience so it would be worth > > considering even for the end user interface. > > What's your definition of "hardware" buttons? Do you consider the > buttons on the Nexus One to be hardware? I don't -- they are > dedicated buttons, but there is nothing mechanical about them. It > really is no different than using the button bar on Honeycomb. Sorry, "hardware" was not the right term to use. I have no hands-on experience with Android past 2.2 so I didn't realise there are on-screen system/button/status/whatever bars on Honeycomb. I'm still not sure how exactly those work anyway, especially how they interact with full-screen apps. I guess what I meant was "how to check if the device has a control element that's always there, that the user can operate at any time and that sends KEYCODE_SEARCH". Ordinary hardware pushbutton is OK, "virtual" key (like on Galaxy S or Galaxy Tab or I presume Nexus One) is OK, an on-screen overlay that's never hidden even if the app is full-screen GLES would be OK, too. Sorry for the confusion, hope this makes it clearer. -- 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
