Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
None
-
None
-
37da30b83021869b2fd069ea49d72d89b16c2046
Description
Currently supported bounds behaviors are:
Flickable.StopAtBounds Flickable.DragOverBounds Flickable.DragAndOvershootBounds
These refer to Flickable content moving past the bounds, and do not cover all platform behaviors today – for example fading content (Jolla) and Flipable effect (Android). Flickable should offer API to make custom bounds behaviors as easy as possible. For example, a property describing distance past bounds could be used to control many different effects. The above 3 enum values might make sense for custom effects as well (for example, if the effect were a fade, you might only want it when attempting to drag past bounds and not when flicking past bounds). In that case an additional property might make sense, indicating whether a custom effect is in use.
Attachments
Issue Links
- is duplicated by
-
QTBUG-53936 Flickable: add a property to measure amount of overshoot even when overshoot is disabled
- Closed
- is required for
-
QTBUG-54042 SwipeView needs feedback if end reached
- Open
-
QTBUG-35081 No native controls on Qt 5.2 for Android, not in widgets nor in quick application
- Closed
- relates to
-
QTBUG-35609 Flickable speed and deceleration are not easily customisable
- Closed
-
QTBUG-56317 Pull down to refresh for ListView (Material Design)
- Open