Use new OverlayManager categories
Using this, we split overlays based on their category, so that cutout emulation and theme overlays no longer clash in their respective settings. Bug: 72436677 Test: make ROBOTEST_FILTER=EmulateDisplayCutoutPreferenceControllerTest RunSettingsRoboTests Change-Id: I23f22113351b3948beb9e3a1fb969700852539cc
This commit is contained in:
@@ -33,9 +33,9 @@ import android.support.v7.preference.ListPreference;
|
||||
|
||||
import com.android.settings.R;
|
||||
import com.android.settings.TestConfig;
|
||||
import com.android.settings.display.ThemePreferenceController.OverlayManager;
|
||||
import com.android.settings.testutils.FakeFeatureFactory;
|
||||
import com.android.settings.testutils.SettingsRobolectricTestRunner;
|
||||
import com.android.settings.wrapper.OverlayManagerWrapper;
|
||||
|
||||
import org.junit.Before;
|
||||
import org.junit.Test;
|
||||
@@ -70,7 +70,8 @@ public class ThemePreferenceControllerTest {
|
||||
when(mContext.getString(R.string.default_theme))
|
||||
.thenReturn(RuntimeEnvironment.application.getString(R.string.default_theme));
|
||||
|
||||
mController = spy(new ThemePreferenceController(mContext, mock(OverlayManager.class)));
|
||||
mController = spy(new ThemePreferenceController(mContext,
|
||||
mock(OverlayManagerWrapper.class)));
|
||||
}
|
||||
|
||||
@Test
|
||||
|
Reference in New Issue
Block a user