Currently supported bounds behaviors are:
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.