'CurrentWorkspaceOnly=true' should also apply to pinned applications

Bug #1248689 reported by Mowgli
70
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Pantheon Dock
New
Undecided
elementary UX
Plank
In Progress
Wishlist
Peter Feichtinger

Bug Description

First time reporting a bug, so please let me know if I'm missing anything. =)

This report is an expansion of comment #6 on this page: https://bugs.launchpad.net/plank/+bug/1053202

When "CurrentWorkspaceOnly=true", Plank should only indicate windows on the current workspace. Currently, this works as stated, but *does not apply to pinned applications*.

My proposal is this: in the case of pinned applications, launched instances on workspaces other than the current one should be ignored, and clicking said pinned item should launch a new instance (or try to, if said app prevents multiple instances).

For comparsion, this exact feature was available in Plank's predecessor, Docky, albeit hidden in the recesses of the Gconf settings (Gconf--> docky-2 | Docky | Items | WnckDockItem | CurrentDesktopOnly).

This might seem trivial, but is a crucial feature for users (like myself) who compartmentalize their jobs into separate Workspaces to manage their workflow more efficiently.

Related branches

Mowgli (mowgli-kun)
summary: - Option to Isolate Dock's Window Management and Workspaces
+ Isolating Dock Window-Management and Workspaces
Mowgli (mowgli-kun)
description: updated
Changed in pantheon-dock:
assignee: nobody → elementary UX Team (elementary-design)
Revision history for this message
Ari (ari-lp) wrote : Re: Isolating Dock Window-Management and Workspaces

Yes! I'd love to see this implemented. Just like Raphael I try to compartmentalize my workflow, having different workspaces for different tasks and way too often I find myself switching back and forth between workspaces when I only wanted to focus another instance of the application on the same desktop.

For me personally this is the only major problem that detracts from an otherwise perfect lightweight dock.

Revision history for this message
Cameron Norman (cameronnemo) wrote :

To clarify the amendment proposed:

You would like the CurrentWorkspaceOnly property to behave how it is now, except in the case of pinned apps, when a new instance will be launched, or at least an attempt will be made to do so.

Revision history for this message
Ari (ari-lp) wrote :

Thank you for your interest, Cameron.

> To clarify the amendment proposed:

> You would like the CurrentWorkspaceOnly property to behave how it is now, except in the case of pinned apps, when a new instance will be launched, or at least an attempt will be made to do so.

Yes, this is about extending this property to pinned applications: What I would like to see (and I think Raphael is with me on this) is an option that will make the dock behave as if there are no other applications open on any workspace other than the current.

In practice this would mean that the dock would hide both instances of non-pinned and pinned applications if they aren't running on the current workspace. This should affect both the visual representation of open windows and window management via the dock.

To clarify:

-- For pinned application launchers:
The launchers should stay pinned. However, instances of open applications on other workspaces should not show up on the dock (neither indicator dots nor entry in context menu list) and any interaction with the dock (scrolling to switch between windows, clicking to minimize/maximize) should only affect the windows on the current workspace.

-- For unpinned application launchers:
The launchers should only show up on workspaces with running instances of the application and just like above they should only visually represent and control instances on the current workspace.

The default behaviour in Plank is window management across all workspaces. 'CurrentWorkspaceOnly' achieves a hybrid between global and isolated window management. What this feature request strives for is the addition of a full-on isolated window management option to the dock, be it as an amendment to the 'CurrentWorkspaceOnly' property or as a completely new property.

Revision history for this message
Mowgli (mowgli-kun) wrote :

Ari and Cameron, both of you are right on the money and express it far more clearly than I ever could.

Basically, with 'CurrentWorkspaceOnly' set to true, Plank should only indicate windows on the active workspace. This should apply to both pinned and unpinned applications. In the case of pinned applications, clicking should launch a new instance (if possible).

Updating the description... =)

Mowgli (mowgli-kun)
description: updated
summary: - Isolating Dock Window-Management and Workspaces
+ 'CurrentWorkspaceOnly=true' should apply to pinned applications
summary: - 'CurrentWorkspaceOnly=true' should apply to pinned applications
+ 'CurrentWorkspaceOnly=true' should also apply to pinned applications
Mowgli (mowgli-kun)
description: updated
Cody Garver (codygarver)
no longer affects: elementaryos
Robert Dyer (psybers)
Changed in plank:
importance: Undecided → Wishlist
Changed in plank:
status: New → Confirmed
Revision history for this message
Peter Feichtinger (shippo) wrote :

I'm working on this, I hope it's OK to assign it to me.

Changed in plank:
assignee: nobody → Peter Feichtinger (shippo)
status: Confirmed → In Progress
Revision history for this message
Henrique Arthur (hnrq) wrote :

Any progress on this?

This feature is a must for me.

Revision history for this message
opuoigsa (opuoigsa) wrote :

This is really the only deal breaker for me for switching to elementary OS or even Ubuntu Mate. It's just that Dash to Dock on Gnome works flawlessly and especially because of this feature. It would be amazing to have it in Plank!

Revision history for this message
deusexmachina (abbelwoi) wrote :

I wouldn't consider this to be something for the wishlist, because the option says "Restrict to workspace" and it doesn't do it imho. What's the status on this issue? This makes using different workspaces unnecessary hard and the fix should be simple.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.