Fixed
Status Update
No update yet.
Comments
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().
na...@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
Currently, when using
SavedStateHandleAPIs such asget(key): T,getLiveData(key): MutableLiveData, andgetStateFlow(key): StateFlowsimultaneously with a matchingkey, theSavedStateHandlesynchronizes the value between them.However, synchronizing between a
MutableStateFlowand aMutableLiveDatawould be very challenging, and now thatSavedStateHandleis Multiplatform,MutableLiveDatais not available in Kotlin Multiplatform.For this reason, we have decided to:
getMutableStateFlow(key): MutableStateFlow.getMutableStateFlow(key): MutableStateFlowand agetLiveData(key): MutableLiveDatamutually exclusive.Therefore, once a
keyis used by one of the two methods, attempting to get the other with the same key will result in an exception.Please note that
getStateFlow(key): StateFlowwill remain unchanged and is not mutually exclusive withgetLiveData(key): MutableLiveDatato maintain backward compatibility.These changes will also address the following feature requests: