fix(TargetDevice): support immediate event writes #276
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 change adds immediate event writes to all target devices, significantly reducing input latency. In the previous implementation, input events are queued in a channel and only processed after the defined polling interval (typically between 1-8ms). This could cause input latency up to the duration of the polling interval.
This implementation removes that potential latency by splitting up the reading/writing into two separate tasks. The writer task will process writes as they come in and dispatch them to the target device implementation immediately instead of waiting for the next polling interval.