David Barth wrote:
> The behavior implemented as of 0.9.8 is to attach the notification
> to the panel, next to the status indicators. It seemed to be the
> most familiar and consistent default position for notifications.

Personally, I'm happy for it to be like that - it's just not working
that way that the moment :)

> If the panel spans the two screens, then notifications are displayed
> on the monitor on the right, along with other system indicators. If the
> panel is only on one screen, because you have then arranged on top
> of each other, then you will see the notifications on the top screen.

Panel is restricted to my primary monitor only which is on the right.
If you view the attachment, apart from being in complete awe of my art
skills, you can see a mock-up of what my screen setup is.

> Note that we only support multihead with RANDR, ie with a single X
> screen spanning multiple monitors, ie what most people use nowadays.
> Of course, we'll try to had support for multiple X screens soon, and also
> welcome patches for that.

TwinView only uses a single X server - it multiplexes the screens
together but at the same time gives the window manager hints, for
example, that maximising a window should only fill one screen.  If you
look at Oli's last comment above, you'll see that he is also using
TwinView, his notifications are also showing on the left monitor, but
unlike me his left monitor is also his primary monitor.  I have not
looked at the positioning code for the notifications (it's getting late
here), but it is possible that the positioning code is always detecting
the right-hand side of the left hand monitor as the position to be,
regardless of what TwinView sets as the primary/second monitors.  This
same problem occurs with AWN, and up until recently with Gnome-Do.

** Attachment added: "twinview setup.PNG"
   http://launchpadlibrarian.net/24863413/twinview%20setup.PNG

-- 
regression vs. notification-daemon: positioning when multiple screens are 
available
https://bugs.launchpad.net/bugs/331369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to