Input test function for Remote RetroPad #16357
Merged
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.
Description
Add input test capability for Remote Retropad core:
Since the Remote Retropad does not support content loading, the only way to pass the
.ratst
file is to invoke RA from command line:retroarch -L netretropad <testfile.ratst>
This will result in a sequence where user is instructed to activate inputs / axes one after the other:
Combined with --max-frames, --appendconfig, a bit of log parsing, and test input driver(s) - to be created separately -, it can serve as a test harness for input related functions.
Already in the present form, it can be used for manual troubleshooting, by asking the user to start the remote pad, try to send inputs, then press A+B which will print a short summary to log. Some combo inputs are recorded explicitly (d-pad diagonals, opposing directions, and the combos currently selectable for menu/exit).
[libretro INFO] [Remote RetroPad]: Validated state: 00003dfd combo: 00002a0f
JSON reader functions lifted and adapted from disk_index_file.c . Sample test file supplied, with all current RetroPad inputs.
Related Pull Requests
#16342