diff options
| author | 2024-07-09 13:20:58 +0000 | |
|---|---|---|
| committer | 2024-07-10 08:26:08 +0000 | |
| commit | 72ffc9821c2bb49a501cfa01f221ad8f2b05eb99 (patch) | |
| tree | ddc21116624e517bd8d32dc303c8776e9b054847 /api/api_test.go | |
| parent | 091a00339486134e146a3a47363d711631262f26 (diff) | |
[bc25] Introduce `isShadeLayoutWide` state, and refactor `shadeMode`.
Context:
Many of the calls to `shadeMode` today actually only intend to ask
whether the shade layout is wide (which may be true in both `Split` and
`Dual` shade modes). Examples include:
1. Determining the clock size
2. Determining whether notifications should be shown on the lockscreen
3. Determining the width and position of NSSL
Since `ShadeMode.Dual` doesn't contain the same wide/narrow distinction
that the other modes do, this CL introduces a dedicated state for this,
`isShadeLayoutWide`.
As a consequence, `shadeMode` is now removed from the repository and
becomes a derived state in the interactor. This unifies the impl for
`shadeMode` in both SceneContainer and Legacy impls of
`ShadeInteractor`.
This CL also replaces usages of `shadeMode` in the examples above (and
others) where the code is agnostic to the specific shade mode type.
Flag: com.android.systemui.dual_shade
Flag: com.android.systemui.scene_container
Bug: 338033836
Bug: 351906743
Bug: 340553529
Test: Added unit tests, and existing unit tests still pass.
Change-Id: Ib173492d9435e6b1ce1c97cf6e6e9eda159d92a1
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions