Add Support for CC Surfaces #148
Open
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 is the skeleton to provide support for CC buttons on the WING to trigger Companion actions.
The
SatelliteClientis responsible for communicating and essentially implements the Satellite API. It should be kept agnostic to ports and hosts.The
CustomCommandHandleruses aSatelliteClientto register the surfaces and eventually to read the OSC messages and execute the button presses through the Satellite API.What is Missing
Rambling
Furthermore, I tried something new with this more separated approach. I think this could be useful to some day clean up the main index.ts file by creating specific handler objects for tasks.
My vision is something like this:
Each of the handlers implements its own Timeout events to control the timing and can callback to the function that need to be executed on the level of Companion, e.g.
UpdateVariableDefinitionsI think this will greatly help declutter the main file and will result in cleaner code for the future, as boundaries between functional parts will be clearer.