ev.rotation sometimes jumps 180 degrees #610

Closed
pteromys opened this Issue Jul 19, 2014 · 4 comments

Comments

Projects
None yet
5 participants
@pteromys

Test case using 2.0.1. To reproduce on Nexus 7:

  1. Put down one finger
  2. Put down a second finger
  3. While moving finger 2, lift finger 1.

On the console-logged events, I see the length of ev.changedPointers drop to 1 a couple of events before ev.pointers does. When this happens, the two pointers seem to swap places, i.e. ev.pointers[x].identifer != x (the value of .identifier seems to remain correct, but not the position in ev.pointers).

Would it be enough to add a sorting step to uniqueArray? It only seems to be used in one place anyway.

@jtangelder

This comment has been minimized.

Show comment
Hide comment
@jtangelder

jtangelder Jul 20, 2014

Member

I've just added the sorting to the uniqueArray function. Could you check if it works for you? You need to clone the repo and run npm install && grunt build to get the builded (concatted) version.

Member

jtangelder commented Jul 20, 2014

I've just added the sorting to the uniqueArray function. Could you check if it works for you? You need to clone the repo and run npm install && grunt build to get the builded (concatted) version.

@mkv123

This comment has been minimized.

Show comment
Hide comment
@mkv123

mkv123 Jul 30, 2014

Doesn't fix it. See comments I made in #596 .

mkv123 commented Jul 30, 2014

Doesn't fix it. See comments I made in #596 .

@amatochristopher

This comment has been minimized.

Show comment
Hide comment
@amatochristopher

amatochristopher Aug 13, 2014

I am having this same issue with versions 2.02. Is there a previous version that was not having this issue?

I am having this same issue with versions 2.02. Is there a previous version that was not having this issue?

@bumbu

This comment has been minimized.

Show comment
Hide comment
@bumbu

bumbu Sep 16, 2014

Contributor

I had a somehow similar problem in PhantomJS but it was because of targetTouches.
I fixed it by preserving the original order of events that come from browser.

Contributor

bumbu commented Sep 16, 2014

I had a somehow similar problem in PhantomJS but it was because of targetTouches.
I fixed it by preserving the original order of events that come from browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment