A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

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.

It's not that MAME was built around SDL keysyms vs. keycodes, it's just that its default translation map is waaaay wrong.

As in, Win RawInput input module gives codes of 30-40 for the home row keys a-', SDL input module sends 4,22,7,9,10,11,13, etc.

Just completely and utterly wrong SDL-code-to-MAME-input-code mapping. As I said, only worked through blind luck before.