diff options
author | 2018-06-29 01:14:31 +0200 | |
---|---|---|
committer | 2018-07-02 17:58:10 +0200 | |
commit | 606405180fc02618f0680295f29e92e946277e80 (patch) | |
tree | fb99a83dec587ebebef695c003a1b24c3674a2dc /packages/overlays/DisplayCutoutEmulationDoubleOverlay | |
parent | f83e814b18af93dba58a8498d085c4dbe1efd587 (diff) |
Only use simple rects for cutout region
Otherwise there is a big performance hit in all kinds of
situations where we do operations with the region, specifically
when:
- updating input windows
- insetting the cutout during layout
- touch dispatch
Test: DisplayCutoutTest, WmDisplayCutoutTest
Bug: 110464019
Bug: 110452325
Change-Id: I94a25c3794ecd33b8b7204ca308ac91623498f13
Diffstat (limited to 'packages/overlays/DisplayCutoutEmulationDoubleOverlay')
-rw-r--r-- | packages/overlays/DisplayCutoutEmulationDoubleOverlay/res/values/config.xml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/packages/overlays/DisplayCutoutEmulationDoubleOverlay/res/values/config.xml b/packages/overlays/DisplayCutoutEmulationDoubleOverlay/res/values/config.xml index ca261f98cfae..80c997a46264 100644 --- a/packages/overlays/DisplayCutoutEmulationDoubleOverlay/res/values/config.xml +++ b/packages/overlays/DisplayCutoutEmulationDoubleOverlay/res/values/config.xml @@ -49,6 +49,8 @@ @dp </string> + <string translatable="false" name="config_mainBuiltInDisplayCutoutRectApproximation">@*android:string/config_mainBuiltInDisplayCutout</string> + <!-- Whether the display cutout region of the main built-in display should be forced to black in software (to avoid aliasing or emulate a cutout that is not physically existent). --> |