tearing-control-v1

(index)

wp_tearing_control_manager_v1

protocol for tearing control

Interface
Version 1

For some use cases like games or drawing tablets it can make sense to reduce latency by accepting tearing with the use of asynchronous page flips. This global is a factory interface, allowing clients to inform which type of presentation the content of their surfaces is suitable for.

Graphics APIs like EGL or Vulkan, that manage the buffer queue and commits of a wl_surface themselves, are likely to be using this extension internally. If a client is using such an API for a wl_surface, it should not directly use this extension on that surface, to avoid raising a tearing_control_exists protocol error.

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_tearing_control_manager_v1.destroy

destroy tearing control factory object

Destructor Request
Since Version 1

Destroy this tearing control factory object. Other objects, including wp_tearing_control_v1 objects created by this factory, are not affected by this request.

wp_tearing_control_manager_v1.get_tearing_control

extend surface interface for tearing control

Request
Since Version 1

Instantiate an interface extension for the given wl_surface to request asynchronous page flips for presentation.

If the given wl_surface already has a wp_tearing_control_v1 object associated, the tearing_control_exists protocol error is raised.

ArgumentTypeDescription
idnew_id<wp_tearing_control_v1>

surfaceobject<wl_surface>

EntryValueSinceDescription
tearing_control_exists01

the surface already has a tearing object associated

wp_tearing_control_v1

per-surface tearing control interface

Interface
Version 1

An additional interface to a wl_surface object, which allows the client to hint to the compositor if the content on the surface is suitable for presentation with tearing. The default presentation hint is vsync. See presentation_hint for more details.

If the associated wl_surface is destroyed, this object becomes inert and should be destroyed.

wp_tearing_control_v1.set_presentation_hint

set presentation hint

Request
Since Version 1

Set the presentation hint for the associated wl_surface. This state is double-buffered, see wl_surface.commit.

The compositor is free to dynamically respect or ignore this hint based on various conditions like hardware capabilities, surface state and user preferences.

ArgumentTypeDescription
hintuint<presentation_hint>

wp_tearing_control_v1.destroy

destroy tearing control object

Destructor Request
Since Version 1

Destroy this surface tearing object and revert the presentation hint to vsync. The change will be applied on the next wl_surface.commit.

wp_tearing_control_v1.presentation_hint

presentation hint values

Enum
Since Version 1

This enum provides information for if submitted frames from the client may be presented with tearing.

EntryValueSinceDescription
vsync01

tearing-free presentation

The content of this surface is meant to be synchronized to the vertical blanking period. This should not result in visible tearing and may result in a delay before a surface commit is presented.

async11

asynchronous presentation

The content of this surface is meant to be presented with minimal latency and tearing is acceptable.

Copyright