[Bug 331369] Re: regression vs. notification-daemon: positioning when multiple screens are available
Using notify-osd 0.9.22 and finding that it's still displaying on my secondary screen. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331369] Re: regression vs. notification-daemon: positioning when multiple screens are available
I should add that I'm not using gnome-panel, but using XFCE4 and their panel. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331369] Re: regression vs. notification-daemon: positioning when multiple screens are available
After looking into the source for a bit, it seems that my issue is when it doesn't detect any panels (gnome-panel anyway) it defaults to using workarea fallback which completely ignores multi-head focus-folllow and uses the entire desktop size instead of a specific monitor. I just made changes to the code to make it default to the first monitor (or the focus monitor if defaults_multi_head_focus_follow exists) instead of the entire desktop. My changes are very specific, though. I don't have a top panel (or any gnome-panels for that matter) AND I'm using multiple screens. A more elegant solution would be to look into scenarios where no [?top] panel exists in a multi-head environment and having it fall back to focus-follow or even a specified display through gconf. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
