| 51072a8b6faf6a92dfe3f063caa5fe645c3d8440 |
|
11-Apr-2018 |
Adrian Roos <roosa@google.com> |
DisplayCutout: Draw anti-aliased bounds in soft overlay
To do so, we cannot use the Region from DisplayCutout, because it is conceptionally
a binary Bitmap. Instead, we need the exact curve as a Path.
Also fixes a theoretical bug where the DisplayCutout
was cached even though the display height changed.
Change-Id: I9356f4589186fedc5dc95010c7bd1a1fa20edf5e
Fixes: 77868940
Test: Enable display cutout in developer options, verify the edges look smoth and not jagged.
Test: atest DisplayCutoutTest
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|
| 6a4fa0ec183e20c32e7816f5475e72fa9126356c |
|
05-Mar-2018 |
Adrian Roos <roosa@google.com> |
DisplayCutout: Support more than one cutout
Also makes API more restrictive. Also moves window manager specific
logic out of the framework. Also fixes SystemUI such that it can properly
deal with more than one cutout.
Bug: 74195186
Test: atest DisplayCutoutTest WmDisplayCutoutTest DisplayContentTests WindowFrameTests
Change-Id: Ib7b89e119ce2d3961687579bb81eadce1159a600
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|
| 8d13bf132ce2ce5533da752d56e9f578c65ebbb3 |
|
21-Feb-2018 |
Adrian Roos <roosa@google.com> |
DisplayCutout: Cache inflations from resources
Caches inflations from resources if the parameters did not
change. This increases the hitrate of the rotation variants
cache in window manager, and avoids unnecessairy reinflations
whenever the display changes.
Change-Id: I2ed9a2c259158bf1a6b551b3422534efbfec99c9
Bug: 72444324
Test: atest DisplayCutoutTest
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|
| 242642146dbd762ccd43f8634476f3be9303b863 |
|
19-Feb-2018 |
Adrian Roos <roosa@google.com> |
DisplayCutout: Dispatch all non-zero safeInsets
Ensures that even if the display cutout does not overlap
a window, the safe insets are still dispatched if the window
overlaps any part of the cutout area and the safe insets
are therefore non-zero.
To do that, we need to compute the insets once against the
display size, then only shrink or expand the safe insets
accordingly.
Bug: 73533636
Test: atest DisplayCutoutTest
Change-Id: I1ea449178e29c7effdd92cac78af1a3875ca7e70
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|
| d07bafda2e91ca888d4413fd5b7b476e933a2561 |
|
11-Dec-2017 |
Adrian Roos <roosa@google.com> |
Display Cutout: Make API public
Bug: 65689439
Test: make update-api
Change-Id: I01e73eea819f0b79eea103d7c895265c38f8ff31
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|
| d4970af157733a096c449aa70456bf92db3b7ae8 |
|
10-Nov-2017 |
Adrian Roos <roosa@google.com> |
Display Cutout: Add Cutout to WindowInsets
Adds a facility for communicating the display cutout to
windows. A follow-up CL will make this a public API.
Bug: 65689439
Test: runtest -x $ANDROID_BUILD_TOP/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
Change-Id: I2290adea0130a7e5764a9412616fd3192800e06a
/frameworks/base/core/tests/coretests/src/android/view/DisplayCutoutTest.java
|