wayland-rs
wayland-rs copied to clipboard
Smithay
Rust implementation of the wayland protocol (client and server).
In the previous versions, it was possible to retrieve the opcode from an `Event` with the `MessageGroup` trait. The latest beta version (0.30.0-beta.8) doesn't allow to do so. Moreover, the...
This allows using `Proxy::data` on custom `ObjectData` implementations, and simplifies the implementation of QueueProxyData.
This also fixes some potential missed wakeups when using EventQueue methods in a multi-threaded application.
Calling methods that do not create objects on a Proxy will ignore `InvalidId` errors. This extends that functionality to creation methods. This makes the solution to #530 much simpler (see...
In the latest beta version (0.30.0-beta.8), even though most (if not all, I haven't checked) implementation of `Proxy` are both `Clone` and `Debug`, the trait doesn't mandate them to be...
This also fixes the event_created_child macro to match a `pat` to allow paths and expressions to work.
This PR adds support for generics in delegate macros. Working examples that use the macros are in https://github.com/wash2/client-toolkit
The wire protocol lacked a way to express nullable arrays as distinct from empty non-null arrays, so this was broken in upstream Wayland. Nullable newids were possible in the wire...
https://github.com/Smithay/wayland-rs/blob/master/wayland-client/src/conn.rs > The two main an simple app as for the [Connection](https://docs.rs/wayland-client/0.30.0-beta.8/wayland_client/struct.Connection.html) are: I don't know what this is supposed to mean.
I noticed that the rs server implementation calls `Socket::blocking_flush()` a fair amount, which blocks on `WouldBlock`. I checked the C wayland-server and its `wl_display_flush_clients()` and others seem to all be...
