<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#c15">Comment # 15</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>The existing gdk API needs a way to identify the output from a gdkwindow. Using the last entered output is probably sub-optimal, but bit it's still an improvement over the (previous) current situation where the function would always return the first monitor because its heuristic was based on global coordinates. Granted, it's not perfect but it's a lot less wrong than before. With current xdg-shell protocol v5, there is no better way to even have a hint on which output the surface resides. If we extend that in xdg-shell v6 to get a more precise value (like the output the window is mostly in, for example), then we can use the same gdk_wayland_window_get_wl_output() API to return that (better) value, so I don't agree the API addition in itself doesn't make sense.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>