On Sat, 2007-06-23 at 18:28 +0000, Alex F wrote:
> Ideally, I would like the option for the two displays to "share" the
> same notification area (so anything that binds to it from either
> display
> shows up on both), with maybe the extra candy that clicking a
> notification icon will bring the associated window to the display
> where
> it was clicked, no matter which display it was launched from.
Ahh, that would be nice. Unfortunately, I don't know that it would be
possible given the way that X11 works. Each screen connected and active
(using "standard" multiple display support) is a different $DISPLAY all
of its own. This means that it should be autonomous, for example with
the tray notification areas in each window. Some programs (such as
Metacity) can share information between both displays because it is
specifically written to be aware of how to handle them.
If you open a terminal on each screen, you'll notice that the $DISPLAY
on the first one is :0.0 and on the second one is :0.1---which means
that you can do something like:
$ DISPLAY=:0.1 firefox
... in a terminal on your primary display, and it will bring Firefox up
on the second display (that is, assuming that you do not have an already
running Firefox on the first display; there is a bug somewhere in
Launchpad for that issue, too).
In thinking about it, it seems that the multiple-display issues should
be abstracted at a lower-level, perhaps such as GTK+, so that all GTK+
applications are automatically aware of multiple X11 screens and able to
take advantage of them in a consistent manner. Right now, as I
understand it, each application that wants to be aware of multiple X11
screens has to be taught to be aware of them independently.
--- Mike
--
Michael B. Trausch
[EMAIL PROTECTED]
Phone: (404) 592-5746
Jabber IM:
[EMAIL PROTECTED]
Demand Freedom! Use open and free protocols, standards, and software!
Support free speech---it is the most valuable freedom we have!
--
Notification area does not work with dual head
https://bugs.launchpad.net/bugs/12696
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
