Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
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 <il...@google.com>
ap...@google.com <ap...@google.com> #3
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().
il...@google.com <il...@google.com> #4
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
Version used: 1.1.0-alpha02
We have postponeEnterTransition() to mark that a fragment transition should be postponed, but you usually have to do something like the following to ensure that we don't sit there postponed forever:
var postponed = false
override fun postponeEnterTransition() {
super.postponeEnterTransition()
postponed = true
}
override fun onStart() {
super.onStart()
if (postponed && !startedTransition) {
// We're postponed and haven't started a transition yet, we'll delay for a max of 2000ms
view?.postDelayed(::scheduleStartPostponedTransitions, 2000)
}
}
It would be nice if isPostponed() was made public rather than relying on my flag.