Seperate display listener registration out of constructor to prevent
circular initialization problem. Use builder to make sure
DisplayImeController and DisplaySystemBarsController will be initialized
properly.
Fix: 161963879
Bug: 161655636
Test: make CarSystemUI
Test: atest CarActivityViewDisplayIdCrashTest
Change-Id: I1104f7bc506d1194d8a2c016106647663d4d24ed
There're some classes reaching to DisplayController and IWindowService
through SystemWindows, decouple SystemWindows from these classes and
inject needed instances directly. Update to use view.getContext instead
of injecting context from SystemUI.
Bug: 161655636
Test: atest WindowManagerShellTests
Test: atest SystemUITests
Change-Id: Ic6da21d6e407d222660b86bfb0f975c4f784b7f5
This CL does:
- Add a PipMenuIconsAlgorithm, allowing calculation on the fly for
correct locations of individual icons
- Make it so that when PIP changes its bounds, it updates the location
of the action items accordingly (if needed)
Bug: 160825579
Test: enter PIP, icons are still where they are
Change-Id: I8618f7c5c36c8e09613c126c1ebb20b60e95de58
WM Shell should be compiled against the platform APIs and thus should
leave sdk version empty. The value of platform_apis will be ignored when
module's type isn't android_app, remove it as well.
Bug: 161116823
Test: manual verified it could access to @hide APIs
Test: make WindowManager-Shell
Test: atest WindowManagerShellTest
Change-Id: I145b0d6352a6e10a2f4051a561e65c282374fa7c
