<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland does not support scaling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101193">bug 101193</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;">CC</td>
<td>
</td>
<td>jadahl@gmail.com, ppaalanen@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland does not support scaling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101193#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland does not support scaling"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101193">bug 101193</a>
from <span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span></b>
<pre>First, I don't think this is a Weston issue. Maybe this should be moved to
Xwayland instead?
As for the scaling protocol mentioned in the GNOME bug report, it does exist:
wl_viewport.
*If* Xwayland had some way of knowing that a Window should cover the whole
output but the size is not a match, it could use wl_viewport to let the Wayland
compositor do the scaling, which for a fullscreen game would hopefully
translate into scaling in display hardware rather than a GPU rendering pass.
But, I would also expect problems with input event coordinates if wl_viewport
is used naively.
Maybe Xwayland could support multiple resolutions via RandR by programming
wl_viewport to scale everything back to the native resolution? Setting a mode
via RandR would then be the trigger for switching the scaling settings in
Xwayland globally.
It does feel to me it could be pretty difficult, I don't really know Xwayland
that well.
As for Xwayland actually changing the real video modes on hardware, I'd rather
not have that. Let's not make X11 RandR a Wayland compositor configuration
interface. Likewise, 'xinput' is not a Wayland compositor configuration
interface either.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>