feat: allow chainable msg filters; add MouseThrottleFilter #1544
+62
−45
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.
Changes in this PR
Made some tweaks to message filtering, as I think this will help others. If y'all don't think it will be too useful, or would rather approach it a different way, feel free to close this out.
WithFilter(filter)toWithFilters(filters...)to allow chainable filters, with aMsgFiltertype to clean things up a little.MouseThrottleFilterfilter, to cover throttling of high-frequency mouse messages. This logic is also used in crush here, and one of my apps, and I suspect such functionality will help others improve performance when they don't need the high-frequency tracking.CONTRIBUTING.md.