The home button is not something applications ever see. The back button is always required to be available on the device (even if that is done through an on-screen affordance).
The search button has always been and is still one of many optional extra keys. The menu key until 3.0 was a required key. Starting with 3.0 the platform has been moving to make this an optional key, hence the need for the API to find out about it. On Mon, Oct 31, 2011 at 9:09 PM, albnok <alb...@gmail.com> wrote: > Interestingly, Android SDK 14/version 4.0 introduced: > > > http://developer.android.com/reference/android/view/ViewConfiguration.html#hasPermanentMenuKey%28%29 > > I discovered this with a leaked Google+ 2.0 app that would crash on > loading Chord with a Class. However, the Home, Back and Search buttons > don't get such APIs. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
