A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

So I figured out why Android MAME builds don't accept most key inputs: input_sdl.cpp is crapful, has a wrong default keymap

and relies on SDL_TEXTINPUt to pass alphanumeric chars along rather than SDL_KEYDOWN or SDL_KEYUP. #fml

It's like, gee, we're sending scan codes that are wholly disparate from Win32 scan codes, what did the original author expect to happen

Is MAME geared to be i18n? SDL_TEXTINPUT is more appropriate for non-keypress stuff (like w/Japanese text entry.)

I agree it should be using keycodes instead of scancodes (e.g. SDLK_S not SDL_SCANCODE_S.) This _is_ SDL 2.0, right?

By default, MAME's core expects keys from the OS-dependent layer to map to an 8-bit array of ASCII-like codes.