Module wayland_protocols::wp::relative_pointer

Available on crate feature unstable only.

protocol for relative pointer motion events

This protocol specifies a set of interfaces used for making clients able to receive relative pointer events not obstructed by barriers (such as the monitor edge or other pointer barriers).

To start receiving relative pointer events, a client must first bind the global interface “wp_relative_pointer_manager” which, if a compositor supports relative pointer motion events, is exposed by the registry. After having created the relative pointer manager proxy object, the client uses it to create the actual relative pointer object using the “get_relative_pointer” request given a wl_pointer. The relative pointer motion events will then, when applicable, be transmitted via the proxy of the newly created relative pointer object. See the documentation of the relative pointer interface for more details.

Modules

• zv1
  Unstable version 1