On HTC Hero, long-pressing-menu has a completely different default behavior: it brings up an app switcher with the last six apps. This is available in almost all applications and makes multitasking very convenient.
I develop on a Hero now and have to remind myself this is a non- standard HTC thing. Fragmentation, indeed! Ordinary HTC users are probably so used to this behavior they would consider Android phones without it as broken. :-) On 25 Sep, 10:18, tauntz <tau...@gmail.com> wrote: > The problem with long-pressing-menu not working is this: HTC Hero. It just > does NOT work there with the default keyboard. > I got also reports about people being not able to open the virtual keyboard > on their phones - I suggested them to try long-clicking the menu (following > Romain Guys suggestions) and I thought that everything is fine - till I got > my hands on HTC Hero - you can long-press the menu for 2 days in a row - it > still does not open the virtual keyboard there. > > The bottom line is that due to platform fragmentation there's no "standard" > way to bring up the keyboard - different platform implementations use a > totally different concept for it. If you want to support such devices, you > could detect if a device is a HTC Hero/(or some other device that does not > use long-menu-press) and if it is, then use a different layout in your app > (eg display a button that brings up the virtual keyboard). Or do some other > ugly ugly hacks (I'll burn in hell for suggesting this, right?:P) > > Tauno > > > > On Thu, Sep 24, 2009 at 10:40 PM, Eric Carman <ewcarma...@gmail.com> wrote: > > > Thank you both for your response. > > > If the application is written for Android 1.1, does this change > > anything in regards to "and there is a keyboard selected and it allows > > this"? I would think that in such an app, since it doesn't know about > > soft keyboards, the system soft keyboard would be selected and would > > allow this. But perhaps there is more to this. Are you possibly > > suggesting that they've installed one of the alternate keyboards? That > > would be interesting. > > > Again, this works on an emulator which I've defined to have no > > keyboard, so that is encouraging. At least I think it helps to rule > > out the caveat where the app isn't consuming the event, but I will > > check this out to be sure as I do catch key events - just not long- > > press menu ones, at least not intentionally. > > > I guess now I would need to know what to tell the user to look for on > > their device such that they can get this functionality to work. > > Assuming I can get them to contact me or bother to read my web site. > > > Would the "keyboard selected" refer to the Settings | Locale & Date | > > Keyboard [Checked] option? > > And then I guess I could refer them to the keyboard settings option > > below that to investigate further. > > > Best Regards, > > Eric > > > On Sep 24, 1:14 pm, Dianne Hackborn <hack...@android.com> wrote: > > > Long press menu forces the keyboard to be displayed, as long as the app > > > doesn't completely consume that key event, and there is a keyboard > > selected > > > and it allows this (the default behavior is to allow it). > > > > -- > > > 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 -~----------~----~----~----~------~----~------~--~---
