Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Report bounds instead of size in WindowMetrics

Browse Source 
Use case: Jetpack WM will use them to get the location of windows on
screen and compute the display feature positions in window coordinate
space.

Bug: 150908045
Test: atest FrameworksCoreTests:WindowMetricsTest
Test: atest CtsWindowManagerDeviceTestCases:WindowMetricsTests
Change-Id: Ia08950cd5df35971408e8b17bb27d97d29d0ab9b
Exempt-From-Owner-Approval: API change
This commit is contained in:
Andrii Kulian
2020-03-05 19:34:43 -08:00
committed by Charles Chen
parent 8f36aba1fb
commit 0be1d67b68
25 changed files with 84 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
test-runner/src/android/test/TouchUtils.java
View File

@@ -223,7 +223,7 @@ public class TouchUtils {
public static void dragViewToBottom(InstrumentationTestCase test, Activity activity, View v,
int stepCount) {
int screenHeight =
activity.getWindowManager().getCurrentWindowMetrics().getSize().getHeight();
activity.getWindowManager().getCurrentWindowMetrics().getBounds().height();
int[] xy = new int[2];
v.getLocationOnScreen(xy);