Struct wayland_server::Display[][src]

pub struct Display { /* fields omitted */ }
Expand description

The wayland display

This is the core of your wayland server, this object must be kept alive as long as your server is running. It allows you to manage listening sockets and clients.

Implementations

Create a new display

This method provides you a Display and inserts it into an existing calloop::EventLoop.

Note that at this point, your server is not yet ready to receive connections, your need to add listening sockets using the add_socket* methods.

Create a new global object

This object will be advertised to all clients, and they will be able to instantiate it from their registries.

Your filter will receinve an event whenever a client instantiates this global.

The version specified is the highest supported version, you must be able to handle clients that choose to instantiate this global with a lower version number.

Create a new global object with a client filter

This object will only be advertized to clients for which your client filter closure returns true. Note that this client filter cannot access the DispatchData as it may be invoked outside of a dispatch. As such it should only rely on the client-associated user-data to make its decision.

Your event filter will be receive an event whenever a client instantiates this global.

The version specified is the highest supported version, you must be able to handle clients that choose to instantiate this global with a lower version number.

Flush events to the clients

Will send as many pending events as possible to the respective sockets of the clients. Will not block, but might not send everything if the socket buffer fills up.

The provided data will be mutably accessible from all the callbacks that may be called during this (destructors notably) via the DispatchData mechanism. If you don’t need global data, you can just provide a &mut () there.

Dispatches all pending messages to their respective filters

This method will block waiting for messages until one of these occur:

  • Some messages are received, in which case all pending messages are processed
  • The timeout is reached
  • An error occurs

If timeout is a duration of 0, this function will only process pending messages and then return, not blocking.

The provided data will be mutably accessible from all the callbacks, via the DispatchData mechanism. If you don’t need global data, you can just provide a &mut () there.

In general for good performance you will want to integrate the Display into your own event loop, monitoring the file descriptor retrieved by the get_poll_fd() method, and only calling this method when messages are available, with a timeout of 0.

Retrieve the underlying file descriptor

This file descriptor can be monitored for activity with a poll/epoll like mechanism. When it becomes readable, this means that there are pending messages that would be dispatched if you call dispatch with a timeout of 0.

You should not use this file descriptor for any other purpose than monitoring it.

Add a listening socket to this display

Wayland clients will be able to connect to your compositor from this socket.

Socket will be created in the directory specified by the environment variable XDG_RUNTIME_DIR.

If a name is provided, it is used. Otherwise, if WAYLAND_DISPLAY environment variable is set, its contents are used as socket name. Otherwise, wayland-0 is used.

Errors if name contains an interior null, or if XDG_RUNTIME_DIR is not set, or if specified could not be bound (either it is already used or the compositor does not have the rights to create it).

Add an automatically named listening socket to this display

Wayland clients will be able to connect to your compositor from this socket.

Socket will be created in the directory specified by the environment variable XDG_RUNTIME_DIR. The directory is scanned for any name in the form wayland-$d with 0 <= $d < 32 and the first available one is used.

Errors if XDG_RUNTIME_DIR is not set, or all 32 names are already in use.

Add existing listening socket to this display

Wayland clients will be able to connect to your compositor from this socket.

The existing socket fd must already be created, opened, and locked. The fd must be properly set to CLOEXEC and bound to a socket file with both bind() and listen() already called. An error is returned otherwise.

Add existing listening socket to this display from a raw file descriptor

Wayland clients will be able to connect to your compositor from this socket.

The library takes ownership of the provided socket if this method returns successfully.

Safety

The existing socket fd must already be created, opened, and locked. The fd must be properly set to CLOEXEC and bound to a socket file with both bind() and listen() already called. An error is returned otherwise.

Create a new client to this display from an already-existing connected Fd

Safety

The provided file descriptor must be associated to a valid client connection.

Trait Implementations

Formats the value using the given formatter. Read more

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Convert Box<dyn Trait> (where Trait: Downcast) to Box<dyn Any>. Box<dyn Any> can then be further downcast into Box<ConcreteType> where ConcreteType implements Trait. Read more

Convert Rc<Trait> (where Trait: Downcast) to Rc<Any>. Rc<Any> can then be further downcast into Rc<ConcreteType> where ConcreteType implements Trait. Read more

Convert &Trait (where Trait: Downcast) to &Any. This is needed since Rust cannot generate &Any’s vtable from &Trait’s. Read more

Convert &mut Trait (where Trait: Downcast) to &Any. This is needed since Rust cannot generate &mut Any’s vtable from &mut Trait’s. Read more

Performs the conversion.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.