diff options
| author | 2023-08-16 05:13:50 -0700 | |
|---|---|---|
| committer | 2023-08-21 23:44:15 +0000 | |
| commit | 8546d327326b3899d9dff0393e69a2f3de627fe9 (patch) | |
| tree | fdd56161412fddc06454d4e6cb730209b7e19bd9 /libs/input/PointerController.cpp | |
| parent | 8a5c6453efe75b481bd400fcd2c44e61bfec1ab8 (diff) | |
Detect an activity "replacement" transition and animate accordingly
There's an occasionally-used pattern among some apps where they
want to "replace" the current activity with another one (rather
than just open a new activity). This involves calling startActivity
and finish at the same time. It's technically more-correct to
start the new activity before calling finish; however, in practice
it kinda works (end result is same but it causes WM to do more
work) to finish before startActivity so of-course some
apps do that.
Because of this "out-of-order"ness, we end up with a CLOSE
transit which apparently looks confusing. So, this CL adds
detection for this specific scenario and treats the
transition as OPEN.
Bug: 295727324
Test: Call finish() then startActivity() immediately after.
Change-Id: I5ce06f83f00042a1cff7f32ce5beb4ab50eec191
Diffstat (limited to 'libs/input/PointerController.cpp')
0 files changed, 0 insertions, 0 deletions