Fixed
Status Update
Comments
il...@google.com <il...@google.com>
sa...@google.com <sa...@google.com>
ap...@google.com <ap...@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> #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().
na...@google.com <na...@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
Component used: lifecycle-livedata-ktx
Version used: 2.3.0-alpha03
StateFlow
SharedFlow
LiveData
created by theasLiveData
extension methods onFlow
in FlowLiveData.kt. It would be nice if the initial value was available asvalue
on the createdLiveData
to help reduce unnecessary UI updates that happen when the values arrive on theFlow
after the lifecycle method responsible for creating the initial view has already finished.Here is a failing test for
StateFlow
that should work, IMHO: