mirror of
https://gitlab.freedesktop.org/wayland/wayland-protocols.git
synced 2026-05-23 10:38:11 +02:00
3d27f2033d
Currently, the client has no information on when it should commit its surface for optimal (low latency) presentation. There have been many discussions on how to improve this situation, but they mostly died down because of the complexity of the topic. This implements a different strategy from previous discussions - instead of telling the client when to commit next, the compositor should just communicate the latest time the client could've committed the last frame. This allows the client to estimate when it should commit in the next presentation cycle, without conflicting with potentially more complete future solutions (that could for example handle VRR better). The use case I specifically want to solve with this is nested Wayland compositors, which currently do not have any accurate information for timing commits. Signed-off-by: Xaver Hugl <xaver.hugl@kde.org> |
||
|---|---|---|
| .. | ||
| presentation-time.xml | ||
| README | ||
Presentation time protocol Maintainers: Pekka Paalanen <pekka.paalanen@collabora.co.uk> (@pq)