fix: Handle high polling rate sources#261
Merged
Merged
Conversation
Android's onTouch and onGenericMotion are only called every screen refresh. This means it is tied to your hz. So what android does for high refresh rate devices is it stores them in MotionEvent.getHistoricalAxisValue() and makes you process them all at once on the next screen refresh. See https://developer.android.com/reference/android/view/MotionEvent#batching We used to just completely ignore this so high DPI mice didn't work properly. Hopefully high DPI everything now works properly.
alexytomi
force-pushed
the
feat/misc
branch
2 times, most recently
from
d080c6a to
9070983
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Android's onTouch and onGenericMotion are only called every screen refresh. This means it is tied to your hz. So what android does for high refresh rate devices is it stores them in
MotionEvent.getHistoricalAxisValue() and makes you process them all at once on the next screen refresh.
See
https://developer.android.com/reference/android/view/MotionEvent#batching
We used to just completely ignore this so high DPI mice didn't work properly.
Hopefully high DPI everything now works properly.