Refactored pointer acceleration #67
Merged
Conversation
This file contains 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
Wow! This is so much easier to do now.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Purpose
Make pointer acceleration
More info
It used to require some mental gymnastics to get the pointer acceleration into the state that you wanted. Not only because it required an understanding of the algorythm, but also because the effect of some settings would change depending on the other settings.
Now each setting is independent, consistent, and using scales that will make sense to someone who isn't knee deep in the inner workings.
I've added a few config examples that took a total of about 10 minute to create, and test that they did want I wanted them to do. I'm now using one of those examples on my own setup, and will likely add more as I narrow down exactly what I want.