HTML5 Gamepad Support #1
Open
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.
Hi,
I recently added HTML5 gamepad support to a fork of your JS GB emulator (see link below), and saw that you have a JS GBA emulator as well.
This pull request has an initial gamepad support, though I wasn't sure how to organize some of the code so that it would fit within the structure you have.
No worries if you don't want to merge, but sharing in case you might be interested.
Pull request for GB emulator:
chrismaltby/gb-studio#305
When w3c "standard" mapping is available for the gamepad, buttons will map to the expected locations Otherwise the first 6 buttons map to A/B/Select/Start/L/R.
Gamepad polling only runs when a gamepad is connected to the browser window
Tested in FF & Chrome