Support key specfication in AnimatedContent [197907070]

Fixed

Feature Request

Status Update

No update yet.

Description

ti...@google.com

created issue #1

Aug 27, 2021 01:08AM

AnimatedContent uses targetState as the key for each content. This targetState instance may change for the same screen between saves and restores. As a result, content of the screen will not be able to restore due to the (indirect) parent key change.

To fix this, we may need to support a mapping between targetState to key on the Transition level APIs.

Comments

jb...@google.com <jb...@google.com> #2Sep 22, 2021 09:06PM

Project: platform/frameworks/support
Branch: androidx-main

commit 700259f0afe267dfe78b93db932a3cfd827a119d
Author: Sherry Hu <shuanghu@google.com>
Date: Mon May 10 14:23:09 2021

Add transition motion between fold and unfold.

Bug: 186211031
Test: manual
Change-Id: Id60f07311eca2d94ef91dc28ae45823a475160b4

M slidingpanelayout/slidingpanelayout/build.gradle
M slidingpanelayout/slidingpanelayout/src/androidTest/java/androidx/slidingpanelayout/widget/FoldTest.kt
M slidingpanelayout/slidingpanelayout/src/main/java/androidx/slidingpanelayout/widget/SlidingPaneLayout.java

https://android-review.googlesource.com/1702066

ti...@google.com <ti...@google.com> #3Sep 30, 2021 07:39PM

Indeed Crossfade needs the same support. Thanks for bringing that up. :)

ap...@google.com <ap...@google.com> #4Oct 14, 2021 12:01AM

Project: platform/frameworks/support
Branch: androidx-main

commit 4b91a7fe67a0a791829b42dbccb4e80f7beaaf74
Author: Doris Liu <tianliu@google.com>
Date: Sun Oct 03 20:03:14 2021

Support custom keys in AnimatedContent

This CL adds support for custom keys to be specified for
the target states in AnimatedContent. When different target
states share the same key, there will be no animation switching
between them.

Bug: 197907070
Test: Included

RelNote: "AnimatedContent now supports custom keys so that
content can be saved and restored when using rememberSaveable."

Change-Id: I5c81a70dd1e53a0076f60f32b8ccd615b7b09248

A compose/animation/animation/integration-tests/animation-demos/src/main/java/androidx/compose/animation/demos/AnimatedContentWithContentKeyDemo.kt
M compose/animation/animation/api/public_plus_experimental_current.txt
M compose/animation/animation/src/androidAndroidTest/kotlin/androidx/compose/animation/AnimatedContentTest.kt
M compose/animation/animation/src/commonMain/kotlin/androidx/compose/animation/AnimatedContent.kt
M compose/animation/animation/integration-tests/animation-demos/src/main/java/androidx/compose/animation/demos/AnimationDemos.kt

https://android-review.googlesource.com/1856567

ti...@google.com <ti...@google.com> #5Oct 14, 2021 12:03AM

The CL above provides custom key support for AnimatedContent. The support for Crossfade per requested in #2 will be addressed in a separate CL.

ap...@google.com <ap...@google.com> #6Nov 4, 2021 05:33PM

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-main

commit 0976f7fdea12b12d1ea619402a512a02b24a4db6
Author: Doris Liu <tianliu@google.com>
Date: Thu Oct 14 13:13:58 2021

Support contentKey in Crossfade

RelNote: "New support for contentKey in Crossfade.
ContentKey will be used for equality check by animation system.
Therefore custom diffing on states can be achieved via specifying
appropriate contentKey for different states.

ConentKey will also be used as the key for save & restore content.
"

Fixes: 197907070
Test: Included
Change-Id: I2e055c2b42736633b544b653e9815255578e7169

M compose/animation/animation/integration-tests/animation-demos/src/main/java/androidx/compose/animation/demos/CrossfadeDemo.kt
M compose/animation/animation/src/commonMain/kotlin/androidx/compose/animation/Crossfade.kt
M compose/animation/animation/api/public_plus_experimental_current.txt
M compose/animation/animation/api/public_plus_experimental_1.1.0-beta03.txt
M compose/animation/animation/src/androidAndroidTest/kotlin/androidx/compose/animation/CrossfadeTest.kt

https://android-review.googlesource.com/1880629

Issue 197907070