summaryrefslogtreecommitdiff
path: root/libs/androidfw/ConfigDescription.cpp
diff options
context:
space:
mode:
author Jordan Demeulenaere <jdemeulenaere@google.com> 2023-01-11 15:48:48 +0100
committer Jordan Demeulenaere <jdemeulenaere@google.com> 2023-01-12 16:24:11 +0100
commit9ecb3db788b9f6be586c0f4f90c19d6337a7cd1b (patch)
treeb2fb0ce830c92edc824f75ed00b4ac2dfc2a8415 /libs/androidfw/ConfigDescription.cpp
parent0e7b6e534c1a818d1539e12d2febe2d26b7fa026 (diff)
Revisit how launch animations handle View visibility
This CL refactors the way the ActivityLaunchAnimator and DialogLaunchAnimator handle the visibility of the animated View when that View implements LaunchableView. Before this CL, a View that is animated would always end up being VISIBLE, even if something made that View INVISIBLE or GONE before or during the animation. That is because our animation code would sometimes change the visibility of the View, using View.setVisibility. After this CL, when animating a LaunchableView, all the visibility changes made to the animated View are done using View.setTransitionVisibility instead. That way, a LaunchableView can track all calls to View.setVisibility only and restore the last visibility that was set on the View at the end of the animation. Doing so ensures that all calls made to View.setVisibility have the expected result once the animation is done. Bug: 264728445 Test: DialogLaunchAnimatorTest Change-Id: I5848d42ef94952ecf058d4e895164389e37e0311
Diffstat (limited to 'libs/androidfw/ConfigDescription.cpp')
0 files changed, 0 insertions, 0 deletions