Open
Conversation
Allow a little movement before deciding that a touch is not a click (coded to allow 5 move events - but could be a parameter). This allows sensitive screens (like nexus10) to better register clicks - without this, it is virtually impossible for a user to 'click' as there is always slight movement between touch and release. The downside is that 'flicking' an item to move it slightly, may register as a click also. The sensitivity could be increased (allow fewer moves between touch and release), or parameterised to make it easily for application users to adjust. Or a genuine move could be de-bounced (if a move happens, any potential click is cancelled).
khadorkin
pushed a commit
to khadorkin/jquery-ui-touch-punch
that referenced
this pull request
Apr 19, 2014
|
+1 |
|
Title of commit did not give it away so did not look here first. I just made my own pull request that uses the time of the touch event to determine if it is a click or not. Not sure what is the better approach. |
Author
|
My fix works, but is nothing to write home about(!) - should really be Think it was my first ever pull req, on git hub - so apologies for naff
|
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
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.
Allow a little movement before deciding that a touch is not a click (coded to allow 5 move events - but could be a parameter).
This allows sensitive screens (like nexus10) to better register clicks - without this, it is virtually impossible for a user to 'click' as there is always slight movement between touch and release.
The downside is that 'flicking' an item to move it slightly, may register as a click also. The sensitivity could be increased (allow fewer moves between touch and release), or parameterised to make it easily for application users to adjust. Or a genuine move could be de-bounced (if a move happens, any potential click is cancelled).