Allow reading joystick buttons executables without including all #791
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.
This PR makes it less confusing to add new actions for buttons on the joystick. The problem was that the do_while used to break if it couldn't find a specific button in order.
For example if you specified:
button0 ...
button1 ...
button3 ...
It would only add to the list the buttons 0 and 1 and then break, never including button3. The new logic uses a for loop (we have specified number of buttons) and loops through all of the indexes and tries to add them. This allows for the behavior above to work correctly without changing the existing behavior.