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.
About the Contributor
This pull request is posted on behalf of myself
Type of Contribution
This is a: Feature
Current Behavior
Since #157, it has been possible to send commands in batches. This can be necessary when sending many commands to both avoid retransmits, and to minimise the visual staggering of the changes.
157 solved this for the method of manual construction of the command classes, by allowing multiple to be provided to the sender at once which would then group them and send them in fewer packets.
This works, but leaves out the simpler api of the library.
New Behavior
This adds a new and user friendly way to batch the sending of commands.
The approach I have taken is to pull out the command methods into their own class which can be used in multiple class implementations, to minimise the effort going forward.
This can be used by doing:
Testing Instructions
Other Information
Status