diff options
| author |  Jan Mulder <jlmulder@xs4all.nl> | 2017-06-28 19:55:19 +0200 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2017-06-29 23:21:55 +0900 |
| commit | d6446569af3b70247b3f77acf5247ef0b08a2cdf (patch) | |
| tree | 7a31e9d0050796378840910af9fb8efad372841b /mobile-widgets/qml | |
| parent | b459ccbff75065d42c9dcf81472e515703c40903 (diff) | |
| download | subsurface-d6446569af3b70247b3f77acf5247ef0b08a2cdf.tar.gz | |
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 <jlmulder@xs4all.nl>
Diffstat (limited to 'mobile-widgets/qml')
| -rw-r--r-- | mobile-widgets/qml/DiveList.qml | 2 |
1 files changed, 1 insertions, 1 deletions
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 |