GNOME Bugzilla – Bug 581833
Overview mode not dual screen aware
Last modified: 2010-06-06 21:24:25 UTC
With dual screens, overlay mode gets split between them, with workspaces divided in two. Personally, I think overlay mode would be better just using the first monitor since that's where the Activities button is. There might be an argument for workspaces starting to appear on the 2nd monitor once you have 4 or more workspaces, but even then I'd be tempted to keep everything on the first screen, otherwise where do you stop? With three screens, that's an awful lot of mouse movement to open something on one of the far workspaces.
Sorry, forgot to link the screenshot: http://picasaweb.google.com/lh/photo/tBAAa-CL1HcLWbl0qdTkkA?authkey=Gv1sRgCJDK77aPmuTOpwE&feat=directlink
*** Bug 581832 has been marked as a duplicate of this bug. ***
*** Bug 581834 has been marked as a duplicate of this bug. ***
As discussed in IRC today: - Each monitor will have a separate overview, showing its own workspaces/windows - Only the primary monitor's overview will have the sidebar, and launching things from the sidebar will launch them onto the primary monitor - You can drag things between monitors in the overview just like you can drag them between workspaces, and you can launch things onto a non-primary monitor by dragging them there from the sidebar
*** Bug 597112 has been marked as a duplicate of this bug. ***
There are two paradigms of using multiple monitors: Each monitor is a separate workspace. Several monitors form one huge workspace. (several others form another workspace) I suppose that GNOME Shell is using the first paradigm ? Then how can user achieve the second one ? Hardware driver support ? And what if several adapters from different vendors or just no support in a driver ? P.S. Maybe there are other paradigms that I do not know ? :)
Perhaps we could use that second monitor as extra real-estate? Maybe zeigeist activity journal type stuff? That I think would be more interesting. sri
Even though this is older the other bug has more information. Going to mark as a duplicate. *** This bug has been marked as a duplicate of bug 609258 ***