Still, it seems to me that even with the current architecture, the application itself does not need to be aware of multiple screens: X11 of course is, therefore the window manager can be, therefore the window manager ought to be able to handle the gymnastics of keeping track of application/notification/displayscreen linkages without troubling the application at all, and (it seems to me) without even bothering the GTK+ rendering system with it. GTK+ just has to render GUI elements at whatever coordinates of whatever device the window manager dictates.
A window titlebar already has send-to-workspace functions that (I assume) are handled by the window manager, and notification icons must already have some linkage to the application process which controls the window associated with the icon. Therefore, the window manager ought to be able to display the same notification-icon-list on each display, and when one is clicked, ought to be able to figure out which display the associated window is already on and move it to the display where the click happened, if necessary. Granted, I don't really know much about the guts of this system, so maybe there's some big architectural obstacle I'm not accounting for, but what I'm describing seems totally doable given what I understand to be the GUI hierarchy. Maybe the problem is that separate X11 display-screens (:0.0 vs :0.1 as you mentioned) have thus far been designed to be TOO autonomous? I can see situations where it would make sense to make them separate (you could have a different user logged in to each, in a different room even, without them interfering with eachother, etc). But clearly there is also a need for slightly less independent alternate displays; maybe a new abstraction level needs to be established that allows for only one user session among several displays (the standard desktop dual-monitor setup), but in return allows for more interaction between the two (like shared notification, etc)? -- 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
