- When checking the threshold, make sure that the change in the
interrested dirrection is much more significant that the delta in the
orthogonal direction (hence the `/ 2`)
- Accept all mouse move event as we otherwise don't get them further if
the event was delayed by another SwipeGestureHandler or flickable
- Remove the duration threshold
- Always register the swipe even if the pointer went in another
direction before
- set the current position on the release event (in case there was no
mouve to that position before)
ChangeLog: adjusted threshold in the SwipeGestureHandler
Closes#6344
Probably also helps for #6350
The origin of this proposal is the name of the `swipe-left`, etc.
directional, boolean properties. They're missing another verb in their
name. In principle the right choice would be "recognize". That is what
the type name suggests, that's the term the documentation uses, so the
code should read `recognize-swipe-left: true;`. However that is a long
word. "Handle" is a verb that's simpler. It's also more generic (that's
a downside), but it's otherwise short enough to make things look
"right":
```
SwipeGestureHandler {
handle-swipe-left: true;
swiped => { something.naviate-left(); }
}
```
Therefore this patch proposes to rename the type to SwipeGestureHandler
and prefixes the boolean directional properties with "handle".
2024-09-18 16:37:27 +02:00
Renamed from tests/cases/elements/swipegesturerecognizer.slint (Browse further)
