summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Jordan Demeulenaere <jdemeulenaere@google.com> 2024-07-29 17:29:36 +0200
committer Jordan Demeulenaere <jdemeulenaere@google.com> 2024-07-31 11:34:12 +0200
commit8ad770b757cb3ef13dbedb77bb1234f7bb695d30 (patch)
treeee7b6f744430e43ac6eb046e4cbbd0e05b042fad /libs/androidfw/StringPool.cpp
parent2a3134e6ff155f56b8e31c2e1c480f09b2c8b137 (diff)
Introduce StaticElementContentPicker (1/2)
This CL is a partial revert of ag/27025577, which allowed ElementContentPicker.contentDuringTransition() to return null to indicate that the element is neither transition.fromContent nor transition.toContent. This was needed for movable elements, which needed to know *at composition time* in which scenes/contents an element could be. Once overlays will be introduced, we will still need to be able to do this check but we won't always have a transition when an overlay is shown but not animating. This CL introduces StaticElementScenePicker, which can provide the list of contents in which an element can be. This StaticElementScenePicker must now be used for MovableElements. This CL also converts some MovableElement from keyguard sections into normal Elements. I expect those elements to not be used or not work correctly anyways because these elements are using the default HighestZIndexContentPicker, which does not work well with movable elements that don't specify the scenes/contents in which they can be. Bug: 353679003 Test: atest PlatformComposeSceneTransitionLayoutTests Test: atest MovableElementTest Test: atest MovableElementContentPickerTest Flag: com.android.systemui.scene_container Change-Id: I39a0427de2eaccd133bbf206ed435a801e07e539
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions