Move bind app-keys logic from AppGroup to AppList

[zqq90]

Keep it simple, bind app-keys in AppList is more controllable than in AppList.

And, two fixes:

• drag-drop will break binding of app-keys, even origin logic.
• after drag, AppGroup.isFavapp will become to true, new window will be created when click or press app-keys

wish you like this

[jaszhix]

Ah, good catch - I normally don't use the key bindings, so glad you caught this. I tested and it seems to work well. Thanks.

[zqq90]

@jaszhix
but this only works in last workspace,
I just noticed that, AppList will be created for each workspace.
I can fixed this in next pr.

Are applets singletons ?

[jaszhix]

The appList is created for each workspace only when you switch workspaces, so for me, I have a fairly common workflow of only using workspace one, and ocassionally switching to two, so in that case if there is only one appList created, it seems to work.

You can get the current appList from child classes with:

this._applet.metaWorkspaces[this._applet.currentWs].appList

or use the alias I created in MyApplet:

this._applet.getCurrentAppList()

Edit: As for singletons, there is only one instance of MyApplet, unless a user places multiple instances of ITM on their panels, if that's what you mean. But appList may be created one time, or as many times as a user switches to a workspace, and appGroup will be created for each open app inside appList, and it contains each app's child windows.