Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
il...@google.com
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
ap...@google.com
Should clarify that if I filter out setCurrentPlayTime(0) (or replace it with setCurrentPlayTime(1)) it works well.
Also even with setCurrentPlayTime(0), onAnimationEnd is notified with correct delay (as if the animation has played).
Description
Fragments do not stop you from running both Transitions and Animations at the same time.
Combining both of them on the same Fragment can result in unexpected visual behavior such as the transition and animation blending in unusual ways.
Regardless of which one you choose, there is a way to execute all of the visual effects possible with one that you can do with both (only transitions can do shared elements), so having them together is not needed.
If you set a transition on the fragment itself, it should override whatever animation is set on the transaction.