tst_QQuickListView::flickBothDirections: flick more
If we make flickDeceleration's default value platform-dependent and often larger, this test begins failing because it expects to flick all the way to the end of the ListView. If we flick a longer distance (starting at the lower-right instead of in the middle of the ListView) in the same time, it's more likely to get to the end. An alternative would be to set flickDeceleration back to the old value in this test. Pick-to: 6.5 Change-Id: If85d9502ceef9fbf6fc087240572cc98326453a5 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
This commit is contained in:
parent
cae32cb2ec
commit
0461a51c8e
|
@ -8013,7 +8013,7 @@ void tst_QQuickListView::flickBothDirections()
|
|||
listview->setContentHeight(contentHeight);
|
||||
}
|
||||
|
||||
flick(window, QPoint(100, 100), QPoint(25, 25), 50);
|
||||
flick(window, QPoint(140, 140), QPoint(25, 25), 50);
|
||||
QVERIFY(listview->isMoving());
|
||||
QTRY_VERIFY(!listview->isMoving());
|
||||
QCOMPARE(listview->contentX(), targetPos.x());
|
||||
|
|
Loading…
Reference in New Issue