Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 33c9aa2d32c2f39d0e7a3934cf14f30b5d0c8513
Author: Jelle Fresen <jellefresen@google.com>
Date: Mon Nov 16 15:59:52 2020
Add option to drive clock by MonotonicFrameClock in tests
It is now possible to let the test clock be driven by the
MonotonicFrameClock instead of the Choreographer. This comes at a cost
though: time control is not implemented in this variant. That is OK,
because this is only meant as a temporary solution to investigate moving
all clocks to the MonotonicFrameClock. It will be removed once we moved
over.
Fixes: 173402197
Test: MonotonicFrameClockTestRuleTest
Relnote: "Temporarily added option to let the TestAnimationClock be
driven by the MonotonicFrameClock"
Change-Id: I1403ba3d82adc530d885192aa696c4363456a4c1
M compose/animation/animation-core/api/current.txt
M compose/animation/animation-core/api/public_plus_experimental_current.txt
M compose/animation/animation-core/api/restricted_current.txt
M compose/animation/animation-core/src/androidMain/kotlin/androidx/compose/animation/core/AndroidAnimationClock.kt
M compose/animation/animation-core/src/commonMain/kotlin/androidx/compose/animation/core/MonotonicFrameAnimationClock.kt
A compose/ui/ui-test-junit4/src/androidAndroidTest/kotlin/androidx/compose/ui/test/junit4/MonotonicFrameClockTestRuleTest.kt
M compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/AndroidComposeTestRule.kt
A compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/MonotonicFrameClockTestRule.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/platform/AndroidAmbients.kt
https://android-review.googlesource.com/1500013
Branch: androidx-master-dev
commit 33c9aa2d32c2f39d0e7a3934cf14f30b5d0c8513
Author: Jelle Fresen <jellefresen@google.com>
Date: Mon Nov 16 15:59:52 2020
Add option to drive clock by MonotonicFrameClock in tests
It is now possible to let the test clock be driven by the
MonotonicFrameClock instead of the Choreographer. This comes at a cost
though: time control is not implemented in this variant. That is OK,
because this is only meant as a temporary solution to investigate moving
all clocks to the MonotonicFrameClock. It will be removed once we moved
over.
Fixes: 173402197
Test: MonotonicFrameClockTestRuleTest
Relnote: "Temporarily added option to let the TestAnimationClock be
driven by the MonotonicFrameClock"
Change-Id: I1403ba3d82adc530d885192aa696c4363456a4c1
M compose/animation/animation-core/api/current.txt
M compose/animation/animation-core/api/public_plus_experimental_current.txt
M compose/animation/animation-core/api/restricted_current.txt
M compose/animation/animation-core/src/androidMain/kotlin/androidx/compose/animation/core/AndroidAnimationClock.kt
M compose/animation/animation-core/src/commonMain/kotlin/androidx/compose/animation/core/MonotonicFrameAnimationClock.kt
A compose/ui/ui-test-junit4/src/androidAndroidTest/kotlin/androidx/compose/ui/test/junit4/MonotonicFrameClockTestRuleTest.kt
M compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/AndroidComposeTestRule.kt
A compose/ui/ui-test-junit4/src/androidMain/kotlin/androidx/compose/ui/test/junit4/MonotonicFrameClockTestRule.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/platform/AndroidAmbients.kt
Description
No description yet. Add one.