From d6446569af3b70247b3f77acf5247ef0b08a2cdf Mon Sep 17 00:00:00 2001 From: Jan Mulder Date: Wed, 28 Jun 2017 19:55:19 +0200 Subject: QML UI: only drag a pull down sync, and not flick it Fast flicking to the top of the divelist triggers almost certainly a pull down sync, as the default boundBehavior is DragAndOvershootBounds. Despite being the default QML action, this leads to unwanted pull down syncs (even in offline mode). Setting the boundBehavior to DragOverBounds solves this issue. Now, the user has to explicitly drag the top down to force a pull down sync, and a accidental fast flick is stopped at the upper bound. Signed-off-by: Jan Mulder --- mobile-widgets/qml/DiveList.qml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mobile-widgets/qml/DiveList.qml b/mobile-widgets/qml/DiveList.qml index 0bd9e81d8..75c9587dc 100644 --- a/mobile-widgets/qml/DiveList.qml +++ b/mobile-widgets/qml/DiveList.qml @@ -313,7 +313,7 @@ Kirigami.ScrollablePage { model: diveModel currentIndex: -1 delegate: diveDelegate - //boundsBehavior: Flickable.StopAtBounds + boundsBehavior: Flickable.DragOverBounds maximumFlickVelocity: parent.height * 5 bottomMargin: Kirigami.Units.iconSizes.medium + Kirigami.Units.gridUnit cacheBuffer: 0 // seems to avoid empty rendered profiles -- cgit v1.2.3-70-g09d2