Very odd - the bug never happens if run from eclipse, but always
happens if installed from the apk and run in the emulator seperately
(would never have known about it if I wasn't showing a co-worker
it.... assumed how eclipse ran it was the same). From what I can tell,
onKeyDown just refuses to recognize any initial key click at all in
the latter case (I have set focusable for the View), and I'm out of
time to debug it until later tonight.

Also, as a general update, the game's music now works. I'm having to
use bloated MP3 files as Android doesn't support MIDI when loaded from
a local resource (regardless of what the doc may say). Is the non-
functioning MIDI a known bug? I couldn't find it on the developer
forums.

On Apr 21, 10:36 am, "Steven A." <[EMAIL PROTECTED]> wrote:
> I just realized there is a critical bug in my application (surprised
> no one pointed it out.....). Just in case addendums can be passed
> along to judges or added to the README text file I included:
>
> I messed up the initialization of the opening menu in the game. One
> can keep hitting the "Keycode_Dpad_Center" (the center key of the
> dpad) indefinitely and it won't start despite that being the default
> option shown.
>
> Hitting Up, Down, Left, or Right just once on the dpad will correctly
> initialize the menu and fixes the problem. After that, one can start
> the game or switch menu items without further problem, and the bug
> will not occur again while the application is running.
>
> I'll fix this bug on my site's version of the application shortly for
> others, and update my site's text with the bug information in case a
> judge looks at the site from a README link. I am hopeful that this bug
> won't cause too much of a problem (I would expect the initial reaction
> after being unable to start to be to try to switch the current menu
> item), but I thought it couldn't hurt to post in case it could be
> passed on to avoid confusion.
>
> Thanks!
>
> -------------------------------------------------------------------------
>
> Application name: EDU Blaster
> Submission: 265500022 or 265494084 (same file, just the earlier one
> had the wrong SDK set as it should be sdk_m5-rc14)
>
> --------------------------------------------------------------------------
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Challenge" 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-challenge?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to