Fixed
Status Update
No update yet.
Comments
ja...@google.com
I don't know if this is something that can be changed, but I'll look into it.
tj...@gmail.com
Hmm... it is supposed to work like this, but you are seeing a bug.
ja...@google.com
ap...@google.com
It cou8ld be tricky to get this right because the onAnimationEnd() and onTransitionEnd() often modify the state. We must execute the Runnable only after the state has been changed to its final value.
I think it could be dangerous to make a change, but it is possible to run all the internal listeners first, then run all of the external ones with the Runnable executed between. Again, it wouldn't be safe because we can't guarantee that only the internal listeners change the system state.
Description
The Transition Kotlin extensions target the Framework Transition class which is a bit confusing, as most framework classes are being deprecated in favor of their AndroidX counterparts, Fragments for example.
As it stands, the KTX libraries for Transitions cannot be used with androidx.transition.AutoTransition. Does this mean android.transition.Transition should be used over androidx.transition.AutoTransition?
Thanks.