Allow reading and setting inputs via the HTTP API #371
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
This adds the following features to the HTTP API:
GET /input
for retrieving a list of currently pressed buttons,POST /input
for setting the list of currently pressed buttons (only works in manual mode, same as pressing buttons in the GUI),GET /bot_modes
for getting a list of all available bot modes,Inputs
channel for the events stream, that can be used to subscribe to input changes.I have made use of these new endpoints in the demo page (
index.html
) and also added form controls for bot mode, emulation speed and video/audio toggle.Furthermore, the demo page will react to and relay button presses. Though the key mapping is currently hardcoded to the bot's defaults.
Checklist
--line-length 120
argument