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

Merge "Removing unnecessary QuickSettings clip bounds in split shade" into sc-dev

Browse Source
This commit is contained in:
Michał Brzeziński
2021-04-29 09:14:41 +00:00
committed by Android (Google) Code Review
parent 166400b045 994722522e
commit 4380046455
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
packages/SystemUI/src/com/android/systemui/statusbar/phone/NotificationPanelViewController.java
View File

@@ -2060,7 +2060,8 @@ public class NotificationPanelViewController extends PanelViewController {
int bottom = 0; int bottom = 0;
int left = 0; int left = 0;
int right = 0; int right = 0;
boolean visible = qsFraction > 0 || qsPanelBottomY > 0; boolean visible = (qsFraction > 0 || qsPanelBottomY > 0)
&& !mShouldUseSplitNotificationShade;
int radius = mScrimCornerRadius; int radius = mScrimCornerRadius;
if (visible || !mShouldUseSplitNotificationShade) { if (visible || !mShouldUseSplitNotificationShade) {
if (!mShouldUseSplitNotificationShade) { if (!mShouldUseSplitNotificationShade) {
@@ -2079,11 +2080,11 @@ public class NotificationPanelViewController extends PanelViewController {
} }
} }
// Fancy clipping for quick settings
if (mQs != null) {
mQs.setFancyClipping(top, bottom, radius, visible);
}
if (!mShouldUseSplitNotificationShade) { if (!mShouldUseSplitNotificationShade) {
// Fancy clipping for quick settings
if (mQs != null) {
mQs.setFancyClipping(top, bottom, radius, visible);
}
// The padding on this area is large enough that we can use a cheaper clipping strategy // The padding on this area is large enough that we can use a cheaper clipping strategy
mKeyguardStatusAreaClipBounds.set(left, top, right, bottom); mKeyguardStatusAreaClipBounds.set(left, top, right, bottom);
mKeyguardStatusViewController.setClipBounds(visible mKeyguardStatusViewController.setClipBounds(visible