Bug 136787 - Need option for panel to span multiple screens
Summary: Need option for panel to span multiple screens
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-22 12:06 UTC by Need Real Name
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-28 14:00:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2004-10-22 12:06:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Epiphany/1.4.4

Description of problem:
It would be nice if the panel could span multiple screens.
Currently a panel is needed for each screen.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
x

Additional info:

Comment 1 Mark McLoughlin 2004-10-28 14:00:28 UTC
Best thing to do is add some rationale as to why there's a need for
both behaviours as opposed to one or the other. Alternatively, explain
why you think spanning the entire screen is always the right thing:

  http://bugzilla.gnome.org/show_bug.cgi?id=73475



Comment 2 Need Real Name 2004-10-28 14:12:39 UTC
There is a need for both behaviours because there is a need for both
setups.

If you have two monitors next to each other, with no (or little) join
between the two, then what you really have, in effect, is a single
wide monitor. Spanning the entire screen is the right thing to do.

If you have two monitors near each other, with a gap between them,
then it makes more sense that the monitors are treated separately.

Allowing a panel to be sized horizontally would fix this bug (a
preference would be a nicer fix though).

Comment 3 Mark McLoughlin 2004-10-28 14:20:45 UTC
Sorry, I should have been more clear - please add your comments to the
upstream bug report


Note You need to log in before you can comment on or make changes to this bug.