<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - intel-virtual-overlay: only background image and mouse cursor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68987#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - intel-virtual-overlay: only background image and mouse cursor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68987">bug 68987</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>The repaint algorithm is extremely simple:
1. Register for Damage tracking on the root window of the Intel X server
2. Wait for Damage events
3. Mark the outputs as damaged, and activate a timer
4. Wait for timer to expire
5. Paint damaged regions on remote outputs (essentially GetImage(local root
window), PutImage(remote root window)
Now, that I mention it... It might not be the damage tracking but the timer
that's failing. But to answer your question, the only thing that could perturb
this is if something prevented the Damage from being sent by X or managed to
hide itself from the GetImage. (Neither of which are likely, and would be X or
DDX bugs.)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>