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).
my...@gmail.com <my...@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().
ra...@cubera.ch <ra...@cubera.ch> #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).
il...@google.com <il...@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
vi...@gmail.com <vi...@gmail.com> #6
vi...@gmail.com <vi...@gmail.com> #7
ag...@gmail.com <ag...@gmail.com> #8
ed...@gmail.com <ed...@gmail.com> #9
The API has changed since that project was created in a way that makes the API more robust. I'm hoping that has fixed this...
Description
Component used: lifecycle
Version used: 2.6.0-beta01
Devices/Android versions reproduced on: N/A
launchWhenX
APIs are being deprecated. However, I do not see an alternative for running one-time suspend code.repeatOnLifecycle
does not match "one-time" andwithX
does not support suspend functions.