<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - protocol: Reporting damage in surface coordinates doesn't work with EGL"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78190#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - protocol: Reporting damage in surface coordinates doesn't work with EGL"
href="https://bugs.freedesktop.org/show_bug.cgi?id=78190">bug 78190</a>
from <span class="vcard"><a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> <span class="fn">Jason Ekstrand</span></a>
</span></b>
<pre>(In reply to Pekka Paalanen from <a href="show_bug.cgi?id=78190#c10">comment #10</a>)
<span class="quote">> My recent reasoning about interface version backward compatibility is an
> argument for not changing wl_surface.damage semantics in a version bump.
> Instead, we should add a new request.
>
> See:
> <a href="http://lists.freedesktop.org/archives/wayland-devel/2014-October/017687.html">http://lists.freedesktop.org/archives/wayland-devel/2014-October/017687.html</a>
>
> "Don't modify old protocol just by version, it won't be backward
> compatible." seems like a good mantra to me.</span >
The only reason why changing damage coordinates would work is precicely because
it's not backwards compatable. Backwards is broken. If we add a new request,
then EGL implementations will continue to happily report damage in buffer
coordinates to the request that needs surface coordinates and ignore the one
that takes buffer coordinates.</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>