You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 9, 2019. It is now read-only.
bkolarov-appolica edited this page Apr 11, 2017
·
4 revisions
You know that the transaction that has been pushed to the back stack will stay the same and it will be executed when popping it. This means that if it has been pushed with an animation, it will be popped with it too.
In order to disable an animation, FragmentController requires its children to implement TransitionAnimationManager. This interface has only one method:
void disableNextAnimation() - Called by FragmentController when you want to pop your fragment without animation but it was previously pushed with such one. Implementation of this method should disable it.
So you either have to think of an implementation of this interface or you could use ours by extending DisabledAnimationFragment. DisabledAnimationFragment implements TransitionAnimationManager so if you choose this approach, you shouldn't bother about disabling the animation.
Please note, that we're open to other solutions for this problem.