Ah, I see, well having that fixed does indeed help a good deal with my problem with the exception of DPAD Center. I wonder why the Center button is not considered a valid DPAD key for returning to keypad mode as well?
Anyway.... thanks for posting and letting me know - appreciate it! On Apr 22, 3:21 am, hanni <[EMAIL PROTECTED]> wrote: > Hi! > > I believe this problem is due to a issueI have been following closely, > issue #319. In my application, after using the touch device, the first > DPAD keypress is consumed completely and there is nothing to do about > it. The bug should be fixed now and the fix should be included in the > next release of the SDK. > > http://code.google.com/p/android/issues/detail?id=319&can=5&colspec=I... > > On 22 Apr, 03:16, "Steven A." <[EMAIL PROTECTED]> wrote: > > > > > Thank you. :) > > > Is there a way for an application to dynamically indicate which > > control mode it desires while running? > > > On Apr 21, 8:51 pm, Esteem <[EMAIL PROTECTED]> wrote: > > > > android's touch mode and keypad mode are not active at the same time. > > > if the current mode is touchmode, you need to press a keypad button to > > > activate the keypad mode. > > > > On Apr 21, 3:39 pm, "Steven A." <[EMAIL PROTECTED]> wrote: > > > > > I posted this on another group, but it is more fitting to discuss this > > > > here. The below instructions work for either Snake or Lunar Landing > > > > (besides also effecting my own app). Please note that one must do the > > > > adb install to the emulator - the bug does not exist running it from > > > > eclipse. All instructions of direction refer to either the arrow keys > > > > on the keyboard or manually clicking on the DPAD on the phone. > > > > > Basically - start the emulater, do "adb install LunarLander.apk" or > > > > "adb install Snake.apk" in the directory with those apks, and then run > > > > that application in the emulater. Hit "up" once and notice the game > > > > does not start as it should. Hit "up" again and notice that it does > > > > run on a second attempt. > > > > > Repeat the steps, only hit "right" for the first keystroke, and "up" > > > > for the second for it to start. > > > > > Try it again with "DPAD Center" or any of the qwerty keypad buttons, > > > > and then hit "up". Notice the game doesn't start as it should, and > > > > will only start when "up" is hit again. > > > > > You can also go into the onKeyDown on LunarLanding.apk, delete > > > > everything, and just have: > > > > doStart(); > > > > return true; > > > > > It will not activiate until one hits Left, Right, Up, or Down first, > > > > and then another key. > > > > > To summarize: onKeyDown does not receive events until Left, Right, Up, > > > > or Down are pressed first in these examples if installed using adb > > > > outside eclipse. Anyone have an explanation as to why, or is it a bug > > > > in the current SDK?- Hide quoted text - > > > > - Show quoted text -- Dölj citerad text - > > > - Visa citerad text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
