This repository was archived by the owner on Oct 8, 2021. It is now read-only.
Bug 1992; Swipe threshold constants are configurable #2015
Merged
Conversation
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
|
This looks great. I'll pull it in. Thanks! |
scottjehl
pushed a commit
that referenced
this pull request
Jul 10, 2011
Fixes #1992; Swipe threshold constants are configurable
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pretty straightforward replacement of hard coded constants modeled on the vkmouse code.
At this point, I wouldn't advocate for these constants to be documented / relied on - but rather a "use at your own risk", might change down the road kind of thing.
Hope this is useful - and in any case we appreciate the work you folks are doing on JQM.