diff options
| author | Evan Rosky <erosky@google.com> | 2020-07-14 09:06:51 -0700 |
|---|---|---|
| committer | Evan Rosky <erosky@google.com> | 2020-07-14 13:42:06 -0700 |
| commit | 4f83ff47a9d10b56b7d62fc4b29b7cb30df17aa6 (patch) | |
| tree | 71f7b4c0fe49a3671f3627d3506d413300cd42d3 /startop/scripts/app_startup/lib/adb_utils.py | |
| parent | c232251896e7971ab0f3163d3dd162fb8ff247d4 (diff) | |
Use keyguard state directly instead of trying to remember it
When updating the divider, this was using the last-remembered
hidden state of the dividerview. The only user of hidden state
was keyguard. Sometimes, split-screen would be dismissed
before keyguard was dismissed. In this situation, the divider
state wouldn't be updated properly. So, instead of trying
to use the potentially incorrect state, always just check the
keyguard directly to determine hidden state.
Bug: 161170237
Test: put 2 apps in splitscreen, lock screen, open emergency,
then unlock, go to splitscreen again, re-lock and see
no divider bar.
Change-Id: I470be161e6c712111549959b0f4471867d08a276
Diffstat (limited to 'startop/scripts/app_startup/lib/adb_utils.py')
0 files changed, 0 insertions, 0 deletions