<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - drawing performance worse than X"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763350#c56">Comment # 56</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - drawing performance worse than X"
href="https://bugzilla.gnome.org/show_bug.cgi?id=763350">bug 763350</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=rstrode%40redhat.com" title="Ray Strode [halfline] <rstrode@redhat.com>"> <span class="fn">Ray Strode [halfline]</span></a>
</span></b>
<pre>(In reply to Ray Strode [halfline] from <a href="show_bug.cgi?id=763350#c45">comment #45</a>)
<span class="quote">> I don't think the frame clock timings are used</span >
So just to follow up here. We had a discussion with Owen on IRC. The frame
timings are intentionally unused by the frame clock for regular updates. frame
rate is throttled by the compositor, so we don't need separate timers client
side. The frame timings are mainly for video player type applications such as
this:
<a href="https://git.gnome.org/browse/gtk+/tree/tests/video-timer.c">https://git.gnome.org/browse/gtk+/tree/tests/video-timer.c</a></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>