| 51df04b93e8e362edd867abd7efaf1659b8b8b82 |
|
04-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Port the legacy velocity tracker strategy.
For comparison purposes, port the legacy velocity tracker
algorithm as it behaved prior to ICS.
Bug: 6413587
Change-Id: I7e8e56584dcdb1a3c660ca9d8f9c5bd5d868e449
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| a5b0698231459ac5b54cf8e8952ac5c2b2b2198b |
|
04-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Implement a second order integrating VT strategy.
Bug: 6413587
Change-Id: I51bc7b8cbff22b10b728fc84ee15370e9984dd55
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 18f329e9480fca75210bb7496e5b4bc987b4ad8f |
|
03-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Implement a weighted least squares VelocityTracker strategy.
No change to the default strategy.
Bug: 6413587
Change-Id: I08eb6f9a511e65ad637359b55b5993c26ba93b40
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 53dd12a66884540b87fe428383e2f79d0f5e32ba |
|
01-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Implement an integrating VelocityTracker strategy.
This algorithm better tolerates certain kinds of errors in the
touch input than the least squares strategy but it may underestimate
the velocity of accelerating movements. This algorithm is
mainly of interest as a baseline for testing and comparison with the
least squares algorithm, which remains the default.
Bug: 6413587
Change-Id: I8ddb50084e44875e234717907e5b06d03f59788c
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 9eb7d86181729c3eb769d71123c4ce9ffc868f08 |
|
01-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Make velocity tracker strategy configurable.
This change is very useful for testing purposes because it makes it
easy to compare different implementations to see how they behave.
There is no change to the current default strategy.
Bug: 6413587
Change-Id: I4d8567aa4160571ba9fa397ce419882cd9366749
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 90729403d50488566eb4ae0e09bb1be21979a633 |
|
15-May-2012 |
Jeff Brown <jeffbrown@google.com> |
Detect when pointer has stopped moving.
Some input devices do not generate ACTION_MOVE events while all
pointers have stopped, thereby lulling the VelocityTracker into
a false sense of complacency. Before handling the following sample,
reset the VelocityTracker state so as not to be influenced by
earlier samples before the pointer stopped. The velocity after
stopping is assumed to be discontinuous.
Bug: 6413587
Change-Id: I6387bc036ff141d083d3d17a89e37eeaa3188349
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| dcab190bd23f632f278af448b0c85b4cadcc6692 |
|
15-May-2012 |
Jeff Brown <jeffbrown@google.com> |
Fix pointer indexing issue in VelocityTracker.
VelocityTracker was implicitly assuming that the pointer ids in
a MotionEvent were ordered. That is not necessarily the case
so we need to be careful while copying the pointer coordinates out.
Bug: 6413587
Change-Id: I3b23a954f893eebdf786f2a94207149b092ef036
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 85bd0d62830a098c1bdc720dfdcf4fe1b18b657c |
|
14-May-2012 |
Jeff Brown <jeffbrown@google.com> |
More VelocityTracker refactoring.
Bug: 6413587
Change-Id: Ida1152e7a34d5fe5caab5e6b5e1bc79f6c7a25e6
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|
| 8a90e6e3174083f274538567d851f98478fc83e9 |
|
11-May-2012 |
Jeff Brown <jeffbrown@google.com> |
Minor refactoring before starting on velocity tracker changes.
Bug: 6413587
Change-Id: I5eba2bb57193bff78cb3740de5f87aca0b31d154
/frameworks/base/libs/androidfw/VelocityTracker.cpp
|