Closed EGjoni closed 7 years ago
I'm going to add a bit of class-level comments in AnimationConfigurationManager about what can be controlled by its APIs.
Specifically, you have fine-grained controls over two classes of animations:
It would add too much runtime overhead to support such fine-grained control to every base facet (rollover, selection, press) of every single view. That is why you cannot turn off rollover animation, for instance, for a specific button.
I'm a bit unclear. Does this mean that progressbar interpolation animations cannot be disabled?
On Tue, Jun 27, 2017 at 9:34 AM, Kirill Grouchnikov < notifications@github.com> wrote:
Closed #28 https://github.com/kirill-grouchnikov/substance/issues/28.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kirill-grouchnikov/substance/issues/28#event-1140509847, or mute the thread https://github.com/notifications/unsubscribe-auth/ABSno-rM4HvBSKQbc7VlFlEZCN2KoXHvks5sIQTfgaJpZM4OE3LO .
Correct. You can call AnimationConfigurationManager.setTimelineDuration and pass 0, but that would effectively disable all Substance animations.
Can't find anything in the docs about how to disable progress bar animations (specifically, how to prevent the progress bar from animating an interpolation between the old value and the new value after setValue() is called).
Docs state that
AnimationConfigurationManager.getInstance().disallowAnimations(.., ..)
can be used to disable animations on components. But animations persist when doing something like the following:
I'm not sure if AnimationConfigurationManager is broken or if I'm just misunderstanding how to use it properly