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).
pa...@gmail.com <pa...@gmail.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().
ap...@google.com <ap...@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).
jb...@google.com <jb...@google.com> #5
@
I think that is intended for Animator. If you set the currentPlayTime
to 0 or the total duration the animator completes. We do some
Description
Component used: Fragment Version used: 1.3.0-beta01
With lib Fragment version 1.2 it is now recommended to use FragmentContainerView instead FrameLayout but that requires FragmentActivity.
Not sure why this requirement was introduced? In our use case user can use app on phone or mirror app to remote device with means DisplayManager.createVirtualDisplay . In both cases we use same stack of fragments, there is no need to run activity in second flow.
Can we bring this functionality back?