summaryrefslogtreecommitdiff
path: root/packages/SystemUI/src/com/android/systemui/qs/QSContainerImplController.java
Commit message (Collapse)AuthorAgeFilesLines
* Prepare to remove new headers flagFabian Kozynski2023-02-221-5/+1
| | | | | | | | | | | | | | | | | | | | | This CL sets everything up for removal of the flag. In particular: * Shortcircuits any conditional the flag was in to true. * Removes all the header views and code from QuickStatusBarHeader and controller. This still exists because it contains QuickQSPanel and refactoring is outside of the scope of this CL. * Renames LargeScreenShadeHeaderController to ShadeHeaderController * Replaces the view with a MotionLayout unconditionally * Removes dimens that were explicitly for combined headers and applies them to the default dimen. * Combines LargeScreenShadeHeaderControllerTest and LargeShadeHeaderControllerCombinedTest into ShadeHeaderControllerTest * Adds the views to the NotificationPanelUnfoldAnimationController Bug: 254512321 Test: SystemUITests Test: QS PlatformScenarioTests Change-Id: I578b82571dc91a9e31c196f3affe60d84c64a1fe
* Fix vertical size when using new headersFabian Kozynski2022-11-021-2/+5
| | | | | | | | | | | For the new headers, we shouldn't be looking at quick_qs_offset_header. Instead, use 48dp for QQS offset. This is needed because with combined headers, the height of the header is always the same. Without this CL, in some devices, there's a lot of blank space under the header, because the system expects them to be larger. Test: manual, multiple devices and screen sizes Bug: 215584502 Change-Id: Ic6f4c45eb4e21891a073f11bb328497a7807edac
* Analyze vertical swipes on QS's Scroll View.Dave Mankoff2022-09-201-2/+29
| | | | | | | | | | | | | | | | | When media controls are shown, the full qs+media controls often takes up more than one full screen. Swiping up on this causes the qs to vertically scroll instead of collapse. Prior to this cl, we weren't analyzing such swipes in the FalsingManager. Now we do. No explicit action is taken in the event of a false swipe. It simply gives us more signal. Enough bad swipes may implicitly cause the lock screen to reset itself. Fixes: 241708312 Test: manual Change-Id: I5adfb3a22b2f0f51efb87d56a6cfc5459cd67006
* Finish removing NEW_FOOTER flagFabian Kozynski2022-04-041-8/+3
| | | | | | | Test: atest SystemUITests Test: manual Fixes: 220344583 Change-Id: I0b188bba6846a4dd935747893232bafa41be3a7d
* Clip UMO in overlay and animate FooterActionsFabian Kozynski2022-03-171-3/+8
| | | | | | | | | The footer actions fade in at the end of the expansion instead of after. Fixes: 224976875 Test: manual Change-Id: I8231b83dda77d2e35655eb7f460c61a9e0ed3f29
* Animating the qs / notification bounds now when dismissing mediaSelim Cinek2021-06-281-6/+0
| | | | | | | | | Previously the bounds animation was on the background which doesn't exist anymore. Fixes: 192059748 Test: add media, dismiss, observe normal animation Change-Id: I0f90b3ca5224b538c62adf30081ad30ed906b3b1
* 9/N Remove MediaHost from QSPanelDave Mankoff2020-11-181-2/+2
| | | | | | | | | QSPanel no longer requires a MediaHost to be injected. Bug: 168904199 Test: atest SystemUITests Change-Id: I6f8c54bb8a1276885cd4617c7d66e1b5f2648153
* Use QSPanelController in QSContainerImplDave Mankoff2020-11-041-2/+27
| | | | | | | | | | The QSContainerImpl was accessing the QSPanel directly and, in turn, accessing some of its injected members. By proxying calls through the controller, we should be able to remove the injected members. Bug: 168904199 Test: manual Change-Id: I3aa379f2b64aca12079281096d8134db58031e84
* Change ViewController#initInternal to #onInitDave Mankoff2020-10-231-1/+1
| | | | | | Bug: 171472009 Test: manual Change-Id: Iddc6c0240486b0d3005216bba0c40bfb481b94b3
* Add initInternal to ViewController.Dave Mankoff2020-10-221-2/+1
| | | | | | | | | | | | | | | | | | | ViewController's init method was not ideal to override. On the one hand, if you put a call super.init() first your onViewAttach method is called before you're subclass's init. Further, if you put your own code befer super.init(), you are still left with the problem that your init is not automatically idempotent, and multiple calls to #init() could result in multiple executions of your code unless you handle it yourself. With this change, #initInternal() is introduced, giving ViewControllers a place to put their run-once code such that it runs before any view-attachment callbacks are fired. Fixes: 171472009 Test: manual Change-Id: I2e284024c82e3f7c7b6f29f22a1ffa3c8aae9fcb
* 5/N Move QS Tile tracking logic into QSPanelControllerBase.Dave Mankoff2020-10-191-24/+10
| | | | | | | | | | | | | This is a big, sort of hairy CL, but is a big push to completing this series. One notable thing you see happen here is a lot less calls to methods liks "setHost" which late-bind various member variables. Classes such as QSTileHost are available to be injected at constrction time and this CL starts taking advantage of that, removing the need for a lot of null checks. Bug: 168904199 Test: atest SystemUITests && manual Change-Id: Ib4768d10e26debdea8d43daee61d2501ed250e67
* 1/N Remove Injection from QSSBHeaderDave Mankoff2020-10-011-5/+19
| | | | | | | | | | First pass at removing injected items from the QuickStatusbarHeader, moving relevant items over to its controller. Lots of unused members are removed in this CL as well. Bug: 168904199 Test: atest SystemUITests Change-Id: I10b85e2b14f0ec3cd1988b6184a270209211618a
* Move logic from QSCarrierGroup into Controller.Dave Mankoff2019-11-191-0/+57
This removes the injection into the QSCarrierGroup view and moves it into an associated controller instead. Controllers are added for QSCarrierGroup, QSContainer, and QuickStatusBarHeader, though only QSCarrierGroup does any heavy lifting at the moment. The other controllers are parent controllers that are needed to ensure everything is cleanly initialized when the view is inflated. Bug: 144503618 Test: atest SystemUITests && manual Change-Id: Iee539b492581f84b25811a9ae2d60426b49b075d