+2
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
The existing threshold APIs in ViewConfiguration were designed specific for touch input. Without new min/max fling velocity APIs, devices that are not touch screen will be using the existing min/max fling thresholds. This prevents customizing fling behavior for different input devices like rotary encoders, that wish to have fling behavior different from touch screen devices. The new API allows specifying min/max fling velocities per InputDevice. This allows a more granular level of fling behavior control, allowing each InputDevice to possibly define its own fling properties. The presence of this API in ViewConfiguration (as opposed to in InputDevice) allows setting global policies easily, where an OEM can easily and globally configure fling for a set of devices (e.g. disable fling for all rotary encoders). Bug: 255845489 Test: CTS test Change-Id: I6e08b2ed5e1959346530a1cc3cc3678480c5cdb7