Changing DeepShortcutManager to have a singleton contructor instead

of getting it from LauncherAppState

This follows the design of other managers and makes it easier to access it
from other processes and non-ui thread.

Bug: 33032833
Change-Id: I8ad82ae5b6cc47bae885f9896985675c7dd0d5b8
This commit is contained in:
Sunny Goyal
2016-11-21 16:02:39 +05:30
parent aa8a871e33
commit dde4fd971e
9 changed files with 36 additions and 31 deletions

View File

@@ -51,7 +51,8 @@ public class ShortcutsChangedTask extends ExtendedModelTask {
@Override
public void execute(LauncherAppState app, BgDataModel dataModel, AllAppsList apps) {
DeepShortcutManager deepShortcutManager = app.getShortcutManager();
final Context context = app.getContext();
DeepShortcutManager deepShortcutManager = DeepShortcutManager.getInstance(context);
deepShortcutManager.onShortcutsChanged(mShortcuts);
// Find ShortcutInfo's that have changed on the workspace.
@@ -67,7 +68,6 @@ public class ShortcutsChangedTask extends ExtendedModelTask {
}
}
final Context context = LauncherAppState.getInstance().getContext();
final ArrayList<ShortcutInfo> updatedShortcutInfos = new ArrayList<>();
if (!idsToWorkspaceShortcutInfos.isEmpty()) {
// Update the workspace to reflect the changes to updated shortcuts residing on it.