From dd96a5e4fd4af1d230c474346e73ff56f5475fa0 Mon Sep 17 00:00:00 2001 From: Sunny Goyal Date: Fri, 17 Feb 2017 11:22:34 -0800 Subject: Simplifying Model data load state management Instead of maintaining 3 different states, each tied to a subset of data, maintaing a single state that represents all the data. Individual subset data is invalidated in rare cases and these invalidates are tightly tied to the UI. This also allows us to add new data to the model, without worring about classifying the data into a subset. Bug: 34112546 Change-Id: Id9cb273de35b79e84a2ef8d6556fcf1e72fb4b75 --- src/com/android/launcher3/LauncherAppState.java | 9 --------- 1 file changed, 9 deletions(-) (limited to 'src/com/android/launcher3/LauncherAppState.java') diff --git a/src/com/android/launcher3/LauncherAppState.java b/src/com/android/launcher3/LauncherAppState.java index e0e53a647..2e75579ca 100644 --- a/src/com/android/launcher3/LauncherAppState.java +++ b/src/com/android/launcher3/LauncherAppState.java @@ -134,15 +134,6 @@ public class LauncherAppState { PackageInstallerCompat.getInstance(mContext).onStop(); } - /** - * Reloads the workspace items from the DB and re-binds the workspace. This should generally - * not be called as DB updates are automatically followed by UI update - */ - public void reloadWorkspace() { - mModel.resetLoadedState(false, true); - mModel.startLoaderFromBackground(); - } - LauncherModel setLauncher(Launcher launcher) { getLocalProvider(mContext).setLauncherProviderChangeListener(launcher); mModel.initialize(launcher); -- cgit v1.2.3