Incoherent values for deltaY about jquery.event.move HOT 5 CLOSED

Thanks. That does look a bit suspect. I'll look into it.
On 15 Apr 2013 14:46, "Antoine Louatron" [email protected] wrote:

Hi,

after playing a little with your plugin, I found what seems a bug.
Here is an output of some Chrome logging :

This is just a copy of some consecutive move event properties.

Object {delta: 0, y: 680, start: 686, dist: -6} Object {delta: -1, y: 679, start: 686, dist: -7} Object {delta: -1, y: 664, start: 686, dist: -22} Object {delta: -7, y: 656, start: 686, dist: -30} Object {delta: -7, y: 648, start: 686, dist: -38} Object {delta: -6, y: 641, start: 686, dist: -45} Object {delta: -1, y: 635, start: 686, dist: -51}

deltaY is not coherent with other values. When I used it, animation was
always slower than cursor movement.
I switch my moving animation to distY and everything is ok.

Thanks for your job !

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15
.

from jquery.event.move.

I can confirm this issue as well with latest code from master. Is this library being maintained? I see the last comment is 6 months ago as of this posting.

from jquery.event.move.

Yes, it is being maintained.

Those logs in the original bug report are a little ambiguous what properties he's looking at, but I've had a look and can't reproduce the problem.

If you pull the latest, you'll see I've added a test for deltaX and deltaY in index.html, lines 338 - 362. Load the page in a browser and move the red box and you should see a series of logs reading:

true, true, true, true

It's working perfectly well as far as I can see. The question is, what's happening on your page that is different to this test? If you could provide a reduced test case on jsfiddle or jsbin or a branch of this repo, that would be very helpful.

from jquery.event.move.

Hmm, on the other hand, that test is throwing up some inconsistencies on the iPad...

from jquery.event.move.

Fixed 82ea750

Delta was being calculated from the latest mouse or touch event position, rather than the latest move event position (which updates at the browser frame rate).

Thanks for the reminder @foxbunny, apologies @antoinelouatron for taking so long.

from jquery.event.move.