Sam Lantinga
Sam Lantinga
Yep! We’re working towards the SDL3 launch, and updating SDL_mixer is on the post-launch TODO list. If you’d like to pitch in, feel free!
What controllers are giving you which results?
It looks like for these controllers we are using DirectInput, setting DIPROP_RANGE to the expected axis range, and relying on DirectInput to convert it correctly. Out of curiosity, what values...
This is something we can add later via a differently named macro, so I'm moving it out of the ABI milestone.
We are scoping work for the SDL 3.2.0 release, so please let us know if this is a showstopper for you.
Yes, we should replicate the logic that SDL2 had, after creating a window.
FYI, this reintroduces issues on Steam Deck popping up the on-screen keyboard. We may need to set the hint to prevent enabling the screen keyboard on platforms where we do...
I'm not sure where best to document it, but the mouse ID is only available in relative mode on desktop platforms.
Or you can just treat mouse ID 0 as your default mouse?
I'll go ahead and write up official documentation for the multi-mouse/keyboard feature for SDL 3.2.0, including the various caveats discussed here.