2/N Use KeyguardHostViewController in KeyguardBouncer.

This mostly proxies existing calls through to the view. A few
exceptions were made where it was obvious what to change.

Also, make ViewController take a View type to streamling
initialization a bit more.

Bug: 166448040
Test: atest SystemUITests && manual.
Change-Id: If849ff57c4b8462e07cc9a4b0546fe7d2a6a0c0a

1 files changed, 1 insertions, 3 deletions

diff --git a/packages/SystemUI/src/com/android/keyguard/KeyguardMessageAreaController.java b/packages/SystemUI/src/com/android/keyguard/KeyguardMessageAreaController.java
index 71a28d2944f3..f056bdbb9706 100644
--- a/packages/SystemUI/src/com/android/keyguard/KeyguardMessageAreaController.java
+++ b/packages/SystemUI/src/com/android/keyguard/KeyguardMessageAreaController.java
@@ -22,8 +22,7 @@ import com.android.systemui.util.ViewController;
 import javax.inject.Inject;
 
 /** Controller for a {@link KeyguardMessageAreaController}. */
-public class KeyguardMessageAreaController extends ViewController {
-    private final KeyguardMessageArea mView;
+public class KeyguardMessageAreaController extends ViewController<KeyguardMessageArea> {
     private final KeyguardUpdateMonitor mKeyguardUpdateMonitor;
     private final ConfigurationController mConfigurationController;
 
@@ -32,7 +31,6 @@ public class KeyguardMessageAreaController extends ViewController {
             ConfigurationController configurationController) {
         super(view);
 
-        mView = view;
         mKeyguardUpdateMonitor = keyguardUpdateMonitor;
         mConfigurationController = configurationController;
     }