SDL gamepad semantics #2283
Draft
SDL gamepad semantics #2283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the PR
This will add North/South/East/West and Circle/Triangle/Square/Cross button enum values (which proxy to ABXY), as well as SDL specific inputs that don't exist with GLFW (They will be impossible to trigger when using the GLFW backend)
Related issues, Discord discussions, or proposals
https://discord.com/channels/521092042781229087/587346162802229298/1285662740467417250
https://github.com/dotnet/Silk.NET/blob/main/documentation/proposals/Proposal%20-%20Multi-Backend%20Input.md#25022022
Further Comments
I'm disabled, and can only play a lot of games with gamepads, having the gamepad API limit what actions can be done on a gamepad makes it harder to play the games I enjoy.