commit ae0f99084d890df476e681ad3b85925ee877715f
author Siarhei Vishniakou <svv@google.com> Mon Sep 14 19:23:31 2020 -0500
committer Siarhei Vishniakou <svv@google.com> Tue Sep 22 15:05:02 2020 +0000
tree 85fcf2bbb1f0e2ed37613d2b300cb231a03ee5af
parent b2d6a712e8fbe7cc81696ed38809689727d30ec6

Use std::vector instead of VLA for addMovement

Currently, VLA is used to send data to 'addMovement' in VelocityTracker.
Use std::vector instead. This also helps assert against the number of
pointers present in the idBits.

Bug: 167946721
Test: atest libinput_tests
Change-Id: Ie8aabafe9a407a2b07d3edef4d1fa312510ccdba

libs/input/VelocityControl.cpp

diff --git a/libs/input/VelocityControl.cpp b/libs/input/VelocityControl.cpp
index bcf55b0..2c04d42 100644
--- a/libs/input/VelocityControl.cpp
+++ b/libs/input/VelocityControl.cpp
@@ -66,7 +66,7 @@
         if (deltaY) {
             mRawPosition.y += *deltaY;
         }
-        mVelocityTracker.addMovement(eventTime, BitSet32(BitSet32::valueForBit(0)), &mRawPosition);
+        mVelocityTracker.addMovement(eventTime, BitSet32(BitSet32::valueForBit(0)), {mRawPosition});
 
         float vx, vy;
         float scale = mParameters.scale;