mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2025-10-29 05:40:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

protocol: define content updates and their internal queue

Browse source 
Multiple protocols use the term content update without a fill
definition. It makes sense to define it in the core protocol so that not
every other protocol has to define it.

This is supposed to retain the current semantics and only changes the
documentation while defining new terms.

Signed-off-by: Sebastian Wick <sebastian.wick@redhat.com>
This commit is contained in:
Sebastian Wick 2024-04-03 16:20:47 +02:00 • committed by Simon Ser
parent 6e1db53916
commit 9069af78a7
1 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

20
protocol/wayland.xml
View file

@ -1656,16 +1656,18 @@
<description summary="commit pending surface state"> <description summary="commit pending surface state">
Surface state (input, opaque, and damage regions, attached buffers, Surface state (input, opaque, and damage regions, attached buffers,
etc.) is double-buffered. Protocol requests modify the pending state, etc.) is double-buffered. Protocol requests modify the pending state,
as opposed to the current state in use by the compositor. A commit as opposed to the active state in use by the compositor.
request atomically applies all pending state, replacing the current
state. After commit, the new pending state is as documented for each
related request.
On commit, a pending wl_buffer is applied first, and all other state A commit request atomically creates a content update from the pending
second. This means that all coordinates in double-buffered state are state, even if the pending state has not been touched. The content
relative to the new wl_buffer coming into use, except for update is placed in a queue until it becomes active. After commit, the
wl_surface.attach itself. If there is no pending wl_buffer, the new pending state is as documented for each related request.
coordinates are relative to the current surface contents.
When the content update is applied, the wl_buffer is applied before all
other state. This means that all coordinates in double-buffered state
are relative to the newly attached wl_buffers, except for
wl_surface.attach itself. If there is no newly attached wl_buffer, the
coordinates are relative to the previous content update.
All requests that need a commit to become effective are documented All requests that need a commit to become effective are documented
to affect double-buffered state. to affect double-buffered state.