Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.14.0
-
None
Description
When the flick(xVelocity, qreal yVelocity) method is called that simulates a real flick, the horizontalVelocity and verticalVelocity properties are not set properly, instead of the acceleration values that are passed to the flick(xVelocity, qreal yVelocity) method they contain zeros. With a real flick, everything is fine.
There is also a problem of inconsistency of acceleration signs with artificial and real flick. For example, if I make a real horizontal flick from left to right, then horizontalVelocity is negative and causes a decrease in contentX. But if you call the flick method with negative horizontal acceleration, then contentX grows.