Enable launcher scope restriction to active workspace
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
New
|
Undecided
|
Unassigned | ||
Unity |
Incomplete
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
The launcher reflects the global session state. This has upsides and downsides.
Upside : If you have a single application window open, you can get to it (and it's workspace) with one click.
Downside :
* Some applications are useful with multiple instances open, the web browser being the primary example.
It's not unusual for me to have one or more browsers open on each of my workspaces. Because the launcher reflects global session state, and not workspace state...
** Clicking the browser icon in a workspace where there is no browser window switches back to the last used window - and away from the current workspace
** Intuitively, would prefer a new browser in workspaces where there are none - perhaps this behaviour could be configured on a per-application basis, or a modifier key provided to spawn a new instance - intuitively tried ctrl-click when expected behaviour failed
* The more applications you open, the fuller the launcher gets
** Perhaps it might be useful to be able to configure some application icons to show only at the workspace scope
** Or the inverse, for some applications to be shown at the session scope (e.g. chat clients) and the default being the workspace scope
Needs design discussion. Marking incomplete.