Filip Wiesner
12/01/2021, 8:18 AMAnimatedVisibility
? I tried fade
with tween(duration = 0)
but there is still small delay before the view disappears.Albert Chang
12/01/2021, 8:21 AMEnterTransition.None
and ExitTransition.None
.Filip Wiesner
12/01/2021, 8:24 AMZoltan Demant
12/01/2021, 8:32 AMFilip Wiesner
12/01/2021, 8:41 AMtween(duration = 0)
. It's just not the same as if it's removed from composition with condition directly and has slight delayZoltan Demant
12/01/2021, 8:54 AMFilip Wiesner
12/01/2021, 8:54 AMChris Sinco [G]
12/01/2021, 9:55 AMDoris Liu
12/01/2021, 6:49 PMEnter/ExitTransition.None
is currently handled as an empty transition. In the exit case, it should finish right away (i.e. in a frame). We don't currently short-circuit for None
, so it does take a frame to finish. Maybe it would make sense to treat it as a special case.
@Filip Wiesner Could you share a video of what it looks like when it doesn't work? Curious to see what you are trying to achieve. šZoltan Demant
12/02/2021, 4:44 AMtransitionSpec
even though there is no targetState change, for those scenarios I simply specified Enter/Exit.None
but it also results in the A -> B transition being cut off if the transitionSpec
is called again before the animation finishes, which is often the case when B changes its contents during the transition (e.g. loading, then actual contents).
I ended up always creating an animation instead, so even if the transition goes from B -> B, Ill do the same thing as A -> B; it works almost flawlessly, but in rare cases the wrong transition ends up happening.Doris Liu
12/03/2021, 1:53 AMZoltan Demant
12/03/2021, 6:04 AMcontentKey
is what solved it. I now use it in both this transition, and the "loading then content" one; and Im no longer seeing additional transitionSpec
calls!