(2013/02/15 11:36), Robert O'Callahan wrote:
I created http://people.mozilla.com/~roc/mousemove-freq.html. We get up to
120-ish mousemoves per second on my machine in Firefox, and a bit more in
IE9, but it caps out at 60fps in Chrome which suggests to me they're doing
something like what I suggested already.
In that testcase you can artificially limit mousemove frequency to 60 per
second. It doesn't make much difference to my drawing, athough I'm poorly
coordinately. But wouldn't it make sense for a drawing app to intelligently
interpolate between mousemove points anyway, using splines or something? I
sort of doubt the difference between 60 points per second and 120 points
per second is critical. And I *really* doubt we should design for that
constraint.
I'm not sure if this is a relevant data point but we had an issue[1]
with touch event coalescing on fennec that produced poor results for the
following drawing application on some devices such as the Dell Streak:
http://parapara-editor.mozlabs.jp/test
This application uses splines to interpolate between the points but
still the lack of events produced poor results. It was fixed by turning
off touch event coalescing. See bug 757680.
Best regards,
Brian
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
