Ethan Lee

Moved the check a little closer to the whitelist declaration, to make it easier to keep the whitelist work in one place (in case we do end up adding variables...

If it's possible to prioritize, switching the order to have libusb as the last pass would definitely be enough, since the adapter doesn't show up as a regular device anyhow.

No idea what most of these things are, but I would imagine it falls in line with text_input_v3, which lives in these two areas: https://github.com/libsdl-org/SDL/blob/main/src/video/wayland/SDL_waylandkeyboard.c https://github.com/libsdl-org/SDL/blob/main/src/video/wayland/SDL_waylandevents.c#L1634-L1641

I don't think we have any maintainers with that environment at all - it's either desktop Linux or iOS/Android with nothing in between, so that's probably what's up. If someone...

It's definitely worth looking into - the Wayland landscape is currently in a state where if the author does not have the compositor literally in front of their face at...

That all makes sense to me - that said, someone else will need to look into this: As of today I've signed onto a job that will take me _very_...

Here's our keyboard listener: https://github.com/libsdl-org/SDL/blob/main/src/video/wayland/SDL_waylandevents.c#L1127 Both the keymap and modifiers callbacks will be where all the related activity is.

That array refers to the scancode value AFAIK. From what I remember, the key is a scancode that we're expected to translate, so we make the translation table in keymap/modifiers...

Here's where SDL implements the protocol for input rectangle: https://github.com/libsdl-org/SDL/blob/main/src/video/wayland/SDL_waylandkeyboard.c#L55 This has been checked under other compositors and with ibus, not sure about fcitx. Quick search suggested native Wayland might...

Locking down the last two bytes would definitely help figure out what to do with the rest - I've seen 'h' and 'x' but I dunno what the rest of...