Module wp_tearing_control_manager_v1

protocol for tearing control

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.

Structs

• WpTearingControlManagerV1
  protocol for tearing control

Enums

• Error
• Event
• Request

Constants

• REQ_DESTROY_OPCODE
  The wire opcode for this request
• REQ_DESTROY_SINCE
  The minimal object version supporting this request
• REQ_GET_TEARING_CONTROL_OPCODE
  The wire opcode for this request
• REQ_GET_TEARING_CONTROL_SINCE
  The minimal object version supporting this request