commit-timing-v1

(index)

wp_commit_timing_manager_v1

commit timing

Interface
Version 1

When a compositor latches on to new content updates it will check for any number of requirements of the available content updates (such as fences of all buffers being signalled) to consider the update ready.

This protocol provides a method for adding a time constraint to surface content. This constraint indicates to the compositor that a content update should be presented as closely as possible to, but not before, a specified time.

This protocol does not change the Wayland property that content updates are applied in the order they are received, even when some content updates contain timestamps and others do not.

To provide timestamps, this global factory interface must be used to acquire a wp_commit_timing_v1 object for a surface, which may then be used to provide timestamp information for commits.

Warning! The protocol described in this file is currently in the testing phase. Backward compatible changes may be added together with the corresponding interface version bump. Backward incompatible changes can only be done by creating a new major version of the extension.

wp_commit_timing_manager_v1.destroy

unbind from the commit timing interface

Destructor Request
Since Version 1

Informs the server that the client will no longer be using this protocol object. Existing objects created by this object are not affected.

wp_commit_timing_manager_v1.get_timer

request commit timer interface for surface

Request
Since Version 1

Establish a timing controller for a surface.

Only one commit timer can be created for a surface, or a commit_timer_exists protocol error will be generated.

ArgumentTypeDescription
idnew_id<wp_commit_timer_v1>

surfaceobject<wl_surface>

EntryValueSinceDescription
commit_timer_exists01

commit timer already exists for surface

wp_commit_timer_v1

Surface commit timer

Interface
Version 1

An object to set a time constraint for a content update on a surface.

wp_commit_timer_v1.set_timestamp

Specify time the following commit takes effect

Request
Since Version 1

Provide a timing constraint for a surface content update.

A set_timestamp request may be made before a wl_surface.commit to tell the compositor that the content is intended to be presented as closely as possible to, but not before, the specified time. The time is in the domain of the compositor's presentation clock.

An invalid_timestamp error will be generated for invalid tv_nsec.

If a timestamp already exists on the surface, a timestamp_exists error is generated.

Requesting set_timestamp after the commit_timer object's surface is destroyed will generate a "surface_destroyed" error.

ArgumentTypeDescription
tv_sec_hiuint

high 32 bits of the seconds part of target time

tv_sec_louint

low 32 bits of the seconds part of target time

tv_nsecuint

nanoseconds part of target time

wp_commit_timer_v1.destroy

Destroy the timer

Destructor Request
Since Version 1

Informs the server that the client will no longer be using this protocol object.

Existing timing constraints are not affected by the destruction.

wp_commit_timer_v1.error

Enum
Since Version 1
EntryValueSinceDescription
invalid_timestamp01

timestamp contains an invalid value

timestamp_exists11

timestamp exists

surface_destroyed21

the associated surface no longer exists

Copyright