<p dir="ltr"><br>
On Mar 31, 2013 3:42 AM, "Daniel Stone" <<a href="mailto:daniel@fooishbar.org">daniel@fooishbar.org</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> On 30 March 2013 22:37, Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>> wrote:<br>
>><br>
>> I think this should be re-worded. It's correct, it just seems<br>
>> awkward. For example:<br>
>><br>
>> Input events also carry timestamps in milliseconds. The base for<br>
>> these timestamps is left up to the compositor. Therefore, they should<br>
>> not be compared against anything except other compositor-provided<br>
>> timestamps.<br>
><br>
><br>
> I think 'unspecified' provides a little more clarity than 'left up to the compositor', but that really is bikeshedding. :)<br>
><br>
> Even then though, I think you're guaranteeing too much: I'm not sure we even currently guarantee that timestamps are comparable across all compositor interfaces. They certainly have to be comparable per-interface, but that's it I think. Kristian?</p>
<p dir="ltr">If the timestamps should be comparable cross interfaces we wouldn't be able to use high precision time stamps from page flips and similar time sources as they are not guaranteed to have the same root as the ones from for example evdev.</p>
<p dir="ltr">Jonas</p>
<p dir="ltr">><br>
> Cheers,<br>
> Daniel<br>
><br>
> _______________________________________________<br>
> wayland-devel mailing list<br>
> <a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br>
><br>
</p>