Hello. On the old Transition API, `transition` s h...

# compose

[bruno.aybar]

Hello. On the old Transition API, transition s had onStateChangeFinished callback. Does anyone know if there's a similar callback on the new API?

[bruno.aybar]

I inspected Transition code and seems like that is not supported. I wonder if that could be done here 🤔 or maybe having a callback for that is not a good idea?

[Zach Klippenstein (he/him) [MOD]]

Most of the animation apis have an animation ended event handler that gets a reason

[bruno.aybar]

The new animation (animate*asState(...) ) apis have finishedListener parameters, yes.

However, the transition apis (updateTransition , transition.animate*(..) ) do not. So, when handling transitions, I'm not sure if there's a way to know "all the animations for this transition have ended"

[Doris Liu]

The new transition has a currentState that can be observed. currentState == targetState signals that the transition for all animations has finished. 🙂

[bruno.aybar]

Thanks @Doris Liu! At the beginning it was a bit complicated to wrap my head around transition changes as State updates, but makes sense! I got it working, thank you 🙏

[Doris Liu]

Glad it worked for you! 🙂 Expressing the finished event as a state change makes sequencing transition states a bit nicer, like in this example: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]/androidx/compose/animation/demos/DoubleTapToLikeDemo.kt;l=74

[bruno.aybar]

wooow... yes, that indeed looks pretty. And here I was writing a queue of states to handle sequencing transition states 🙃

[bruno.aybar]

once I'm done with my changes, I would really appreciate your feedback, if possible 😅

[Doris Liu]

once I'm done with my changes, I would really appreciate your feedback, if possible

Sure thing! I'm happy to take a look! 🙂