Fixed
Status Update
Comments
mg...@google.com <mg...@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).
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().
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).
gr...@google.com <gr...@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
The goal here is to:
- Introduce a `Encoder` and `Decoder` that converts a `@Serializable` annotated class into a `SavedState`.
- Introduce new top-level functions that takes in a `@Serializable` and a `KSerializer` for saving state. For example, `savedStateHandle.saveable(key, serializer) { serializable }` (the code is not final, and may change).
- Best effort supporting all types that `@Serializable` supports.
- Consider to add default `Serializer` for Android specific types (e.g., `Size`).