Struct wayland_client::EventQueue

pub struct EventQueue<D> { /* private fields */ }

An event queue

This is an abstraction for handling event dispatching, that allows you to ensure access to some common state &mut D to your event handlers.

Event queues are created through Connection::new_event_queue(). Upon creation, a wayland object is assigned to an event queue by passing the associated QueueHandle as argument to the method creating it. All event received by that object will be processed by that event queue, when dispatch_pending() or blocking_dispatch() is invoked.

Implementations

impl<D> EventQueue<D>

pub fn handle(&self) -> QueueHandle<D>

Get a QueueHandle for this event queue

pub fn dispatch_pending(&mut self, data: &mut D) -> Result<usize, DispatchError>

Dispatch pending events

Events are accumulated in the event queue internal buffer when the Wayland socket is read using the read APIs on Connection, or when reading is done from an other thread. This method will dispatch all such pending events by sequentially invoking their associated handlers: the Dispatch implementations on the provided &mut D.

pub fn blocking_dispatch(
    &mut self,
    data: &mut D
) -> Result<usize, DispatchError>

Block waiting for events and dispatch them

This method is similar to dispatch_pending, but if there are no pending events it will also block waiting for the Wayland server to send an event.

A simple app event loop can consist of invoking this method in a loop.

pub fn sync_roundtrip(&mut self, data: &mut D) -> Result<usize, DispatchError>

Synchronous roundtrip

This function will cause a synchronous round trip with the wayland server. This function will block until all requests in the queue are sent and processed by the server.

This function may be useful during initial setup with the compositor. This function may also be useful where you need to guarantee all requests prior to calling this function are completed.

pub fn prepare_read(&self) -> Result<ReadEventsGuard, WaylandError>

Start a synchronized read from the socket

This is needed if you plan to wait on readiness of the Wayland socket using an event loop. See ReadEventsGuard for details. Once the events are received, you’ll then need to dispatch them from the event queue using EventQueue::dispatch_pending().

If you don’t need to manage multiple event sources, see blocking_dispatch() for a simpler mechanism.

pub fn flush(&self) -> Result<(), WaylandError>

Flush pending outgoing events to the server

This needs to be done regularly to ensure the server receives all your requests.

Trait Implementations

impl<D> Debug for EventQueue<D>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.