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? --~--~---------~--~----~------------~-------~--~----~ 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 [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 -~----------~----~----~----~------~----~------~--~---
