Struct wayland_server::protocol::wl_seat::WlSeat [] [src]

pub struct WlSeat { /* fields omitted */ }

Methods

impl WlSeat
[src]

seat capabilities changed

This is emitted whenever a seat gains or loses the pointer, keyboard or touch capabilities. The argument is a capability enum containing the complete set of capabilities this seat has.

When the pointer capability is added, a client may create a wl_pointer object using the wl_seat.get_pointer request. This object will receive pointer events until the capability is removed in the future.

When the pointer capability is removed, a client should destroy the wl_pointer objects associated with the seat where the capability was removed, using the wl_pointer.release request. No further pointer events will be received on these objects.

In some compositors, if a seat regains the pointer capability and a client has a previously obtained wl_pointer object of version 4 or less, that object may start sending pointer events again. This behavior is considered a misinterpretation of the intended behavior and must not be relied upon by the client. wl_pointer objects of version 5 or later must not send events if created before the most recent event notifying the client of an added pointer capability.

The above behavior also applies to wl_keyboard and wl_touch with the keyboard and touch capabilities, respectively.

unique identifier for this seat

In a multiseat configuration this can be used by the client to help identify which physical devices the seat represents. Based on the seat configuration used by the compositor.

Trait Implementations

impl Send for WlSeat
[src]

impl Sync for WlSeat
[src]

impl Resource for WlSeat
[src]

Pointer to the underlying wayland proxy object

Create an instance from a wayland pointer Read more

Create an instance from a wayland pointer Read more

Pointer to the interface representation

Internal wayland name of this interface

Max version of this interface supported

Current version of the interface this resource is instanciated with

Check if the resource behind this handle is actually still alive

Check of two handles are actually the same wayland object Read more