Joystick support (final) #54
Open
Conversation
This file contains hidden or 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
Added to support mouse scrolling, page up, page down, home, and end
Added filled() and polygon()
Conflicts: examples/timeout.lua
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've re-implemented Joystick support, substituting joystick.count for JOYSTICKS, and re-working the API that was added to be more generally useful outside the scope of Joystick handling.
Joystick rescan is done whenever switching to the editor, meaning end-users can plug joysticks in and re-start their games if needed. Also dynamically adding up to 8 (hard-coded limit of SDL handles reserved) joysticks at rescan. Button support is included.
To use:
joystick.count = number of joysticks detected
joystick[1].x / joystick[1].y = x/y axes
joystick[1].button = 1 for down, 0 for up