Status Update
No update yet.
Comments
mo...@google.com
All extensions in 'core-ktx' target either 'core' or the framework types. This is working as expected. It sounds like this is a feature request for a transition-ktx with equivalent extensions for the androidx.transition types.
> as most framework classes are being deprecated in favor of their AndroidX counterparts, Fragments for example.
"Most"? This *dramatically* overstates what is actually happening. Fragments (and loaders) were added to the framework in a time where the Android team did not have external libraries for shipping features. Transition was added 5 years later.
mo...@google.com
If the Transition api is unlikely to change, there is no need for a transition-ktx for androidx.transition types. If developers should use Androidx transitions over framework transitions where possible however, then it would be much appreciated.
I am well aware of the limitations that existed when Fragments and Loaders were created, and when the Transition api was introduced.
mo...@google.com
Branch: androidx-master-dev
commit ae42e311ecfbac18cedc90e489d1fdde956a4557
Author: Jake Wharton <jakew@google.com>
Date: Fri Nov 22 11:13:30 2019
Introduce transition-ktx for standalone transition library
These extensions are the same as androidx.core.transition for the platform types, just adapted to the standalone library.
Bug: 138870873
Test: gw :transition:transition-ktx:build :transition:transition-ktx:connectedCheck
Change-Id: Ie80022cc60ed1f482b7593db5ef1ac1c5ea33d8d
M buildSrc/src/main/kotlin/androidx/build/PublishDocsRules.kt
M jetifier/jetifier/migration.config
M settings.gradle
A transition/transition-ktx/OWNERS
A transition/transition-ktx/api/1.4.0-alpha01.txt
A transition/transition-ktx/api/current.txt
A transition/transition-ktx/api/public_plus_experimental_1.4.0-alpha01.txt
A transition/transition-ktx/api/public_plus_experimental_current.txt
A transition/transition-ktx/api/res-1.4.0-alpha01.txt
A transition/transition-ktx/api/restricted_1.4.0-alpha01.txt
A transition/transition-ktx/api/restricted_current.txt
A transition/transition-ktx/build.gradle
A transition/transition-ktx/src/androidTest/AndroidManifest.xml
A transition/transition-ktx/src/androidTest/java/androidx/transition/TestActivity.kt
A transition/transition-ktx/src/androidTest/java/androidx/transition/TransitionTest.kt
A transition/transition-ktx/src/androidTest/res/layout/test_activity.xml
A transition/transition-ktx/src/main/AndroidManifest.xml
A transition/transition-ktx/src/main/java/androidx/transition/Transition.kt
mo...@google.com
Passing to Jeremy to get his thoughts
jb...@google.com
What we really need is a signal to say when all transitions are done and with it running early, we don't have that. For fragments this means that we could end up moving the fragment to RESUMED before all the transitions are actually completed and execute some code that is normally fine when the system is settled, but dangerous when it is not.
If moving onTransitionEnd() might be too dangerous are there other options? If you are in the animateToStart case should you even get an onTransitionEnd(). Maybe all external listeners get is an onTransitionCancel() since you are reversing a transition you started in the middle of it. Is that a safer signal to send back?
I think it is okay to separate the signals as long as they are explicit, but we for sure need a way to know that the Transition system is completely done doing any work and our Views are back in the original state that we passed them in.
mo...@google.com
Maybe you could notify at the end of your animateToStart lambda?
jb...@google.com
Per offline discussion, we can move ahead with the solution suggested in
This will change the current order:
start transition > animateToStart > onTransitionEnd() > Runnable > finish up transition work
to
start transition > animateToStart > Runnable > finish up transition work > onTransitionEnd()
This has the implications that if developers are doing something with a specific result in their onTransitionEnd() callback, they will also need to handle the cancellation case by overriding the new onTransitionEnd(Transition, boolean)
For example, if there is a transition from View_A to View_B and the onTransitionEnd() callback has logic that expects View_B to be the final state, it will now need to add some additional logic based on the boolean in the case that View_A is the final state.
mo...@google.com
ap...@google.com
Branch: androidx-main
commit 889b310dee76183e0f89e76d014728f728190740
Author: George Mount <mount@google.com>
Date: Wed Dec 20 14:35:35 2023
Change order of listeners for seeking transitions.
Fixes: 307624554
When TransitionSeekController.animateToStart() is used,
externally added TransitionListeners will have onTransitionEnd()
called after the animateToStart()'s lambda. Internally-added
listeners will be called before the animateToStart()'s lambda.
Test: new test
Change-Id: Ic6a55916958f85d41c54d7739bde09cfc2352d7c
M transition/transition/src/androidTest/java/androidx/transition/SeekTransitionTest.kt
M transition/transition/src/main/java/androidx/transition/Transition.java
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.transition:transition:1.5.0-alpha06
Description
Component used: Transition
Version used: 1.5.0-alpha04
Expected:
When using the new
animateToStart(Runnable)API, I would expect the Runnable to be executed before anyonTransitionEnd()callback that were set on the transition that was being seeked.Actual:
The logs execute inside the
onTransitionEnd()callback before the runnable.Steps:
1a. Use predictive back and cancel the gesture
1b. Launch the app and click the "Animate" button, then click the "Cancel Animation" button