<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body><span class="vcard"><a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> <span class="fn">Olivier Fourdan</span></a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><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#c21">Comment # 21</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 <span class="vcard"><a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> <span class="fn">Olivier Fourdan</span></a>
</span></b>
<pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=766566#c18">comment #18</a>)
<span class="quote">> Yea, it makes sense to keep it private, so that no new place starts to rely
> on something that isn't reliable.</span >
But again, there is no reason for it to be unreliable, we "just" have to add
the relevant missing protocol bits to make it reliable.
<span class="quote">> Should add the "get_monitor_at_window" to the list of things to deprecate
> for GTK4 I guess.</span >
Yet I am not entirely convinced "get_monitor_at_window()" is not useful, even
more when there is no global coordinates like in Wayland, it's pretty much the
only remaining way to identify the monitor, unless we reckon identifying the
monitor is not something clients shouldn't be able to do.
Meanwhile:
<span class=""><a href="attachment.cgi?id=328173&action=diff" name="attach_328173" title="[PATCH] wayland: Make gdk_wayland_window_get_wl_output() private">attachment 328173</a> <a href="attachment.cgi?id=328173&action=edit" title="[PATCH] wayland: Make gdk_wayland_window_get_wl_output() private">[details]</a></span> <a href='review?bug=766566&attachment=328173'>[review]</a> has been pushed as commit <a href="https://git.gnome.org/browse/gtk%2B/commit/?id=0b58c96">0b58c96</a> - wayland: Make
gdk_wayland_window_get_wl_output() private</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>