diff options
| author | ryanlwlin <ryanlwlin@google.com> | 2021-05-27 10:55:19 +0800 |
|---|---|---|
| committer | ryanlwlin <ryanlwlin@google.com> | 2021-06-16 10:53:44 +0800 |
| commit | 430b258b6a56e1b2b557aed3295fe95429ba9e17 (patch) | |
| tree | 75cc75d7fa3f92464ac83706d67c49d26f43d39f /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | ba2d2a3d5ded601122f5cdfdbbb08a9126e93095 (diff) | |
Fix incorrect boundary/appearance after folding the device
When the device is folded, the screen size is changed.
We need to compute the magnification frame and its boundary
based on current window metrics. Besides, to keep
the magnified center, we rescale the former center and apply it
to the center of the new magnification frame.
Folding the device also triggers orietation changes, which is
the unexpected case. To avoid handling this case, we also check
whethe it is the window hieght/width exchanging case.
Bug: 185728667
Bug: 185536537
Bug: 180054792
Test: atest WindowMagnificationControllerTest
manually test with follow cases
1. change display size or font size
2. orientate the device
Change-Id: If2a93ad14bf8e07cf149180e639b35fc0bedfd10
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions