This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The wlr_presentation_feedback struct now tracks presentation feedback
for multiple resources (but still a single surface content update). This
allows the compositor to properly send presentation events even when
there is more than one frame of latency or when it references a
surface's buffer.
Most of the time, compositors just display the surface's current buffer
on an output. Add an helper to make it easy to support presentation-time
in this case.
References: swaywm/sway#4572
Closes: #1917
cc @YaLTeR
Breaking change: instead of calling
wlr_presentation_surface_sampled
at render time andwlr_presentation_send_surface_presented
at presentation time, most compositors now just need to callwlr_presentation_surface_sampled_on_output
at render time. Compositors that callwlr_buffer_ref
need to callwlr_presentation_surface_sampled
when they ref the buffer,wlr_presentation_feedback_send_presented
when this buffer has been presented for the first time and thenwlr_presentation_feedback_destroy
.Sway PR: swaywm/sway#4731