<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=766566#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=766566">bug 766566</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>For the record, these patches break some menu positioning in master with multi-monitor setups because, in various places (including gtkcombobox), gtk compares the monitor returned from the device event's root coordinates against the monitor's position and size returned by get_monitor_at_window(). Since there is no such thing as global root coordinates in Wayland (just fake root coordinates which are toplevel relative), that will not match now that get_monitor_at_window() returns the real monitor. After discussing with Jonas on irc, I'd rather not revert these patches though (they do return the right monitor, whereas before it worked by chance as both get_monitor_at_window() and get_monitor_at() where based on root coordinates, so were equally wrong), because the menu positioning will be entirely reworked to be done in gdk backends so this is will be fixed with <a class="bz_bug_link bz_status_NEW " title="NEW - GTK should let GDK position menus" href="show_bug.cgi?id=756579">bug 756579</a> that will be discussed soon at the forthcoming gtk hackfest...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>