Status Update
No update yet.
Comments
il...@google.com
ke...@google.com
Hi, thanks for reporting this. Please update this ticket with a reproducible code/sample so we can better investigate the issue.
Thanks!
ap...@google.com
The endless joy of support tracker ....
So I'm actually asking a question ... So instead of insta closing without reading anyway to have someone read and answer?
What / Where are the settings that controls the velocity calculations.
Compose animations are tied to Android dev settings animation scale. What is the equivalent here.
ap...@google.com
Not all compose animations are tied to Android developer settings.
Fling animations in lists are no longer controlled by the Settings menu and cannot be overriden, so that shouldn't be source of the problem you're seeing. This has been solved in
The velocity calculation for lists is done at the draggable level and are also transparent to developers, so you cannot control how these are calculated.
A sample/reproducible code is required if I was to move forward with investigating this issue.
ke...@google.com
il...@google.com
I don't have a repro and can't build one, the app is in prod and working for thousands of other users.
Is there any other changes in Compose 1.4 that could impact the velocity calculation?
Description
With the release of
NavigationRailin Material 1.4.O-alpha01, some of the navigation component methods should support the superclassNavigationBarViewinstead ofBottomNavigationViewBottomNavigationView.setupWithNavController(navController: NavController)is an example of a method that needs to be updated.