Preston Carpenter

Honestly for those it's not a big deal since it'll probably never be used by the library user. Just make an unsafe function that returns whatever is in the struct....

The virtual keyboard has [only one event](https://github.com/swaywm/wlroots/blob/master/include/wlr/types/wlr_virtual_keyboard_v1.h#L37). Since it is a destroy event we will need to listen for it and properly destroy any objects we allocate when its destroyed....

This should work, as a means to statically allocate the listeners: ```rust struct Bar; struct Foo { first: Option } static mut foo: Foo = Foo { first: None };...

Adding the unsound tag until I have looked at the code in practice and ensured it is sound.

One issue with this approach is that it effectively adds two code paths to arrive at the same place. Currently, we just use boxed `ManagerHandler` traits to arrive at resource...

Actually now that I work on this more I've come to the rather startling conclusion that the manager handlers don't actually need to be dynamically dispatched ever! There is only...

This patch looks good. Since I'm not maintaining this though I'd rather do one of the following: * hand over write access to this repo to you (would require permission...

> I am actually kinda curious about the state of this project today. What do you think would be the experience of writing a compositor with it now? Using wlroots-rs...

I would like to be able to get the dmabuf frames from the manager. This will neccessitate a pattern similar to [the output and its modes](https://github.com/swaywm/wlroots-rs/blob/master/src/types/output/output.rs#L421). Of importance note the...

Let's expose it as bitflags, since that's more ergonomic for the end user to work with. Repr(c) enums are for FFI and but are less ergonomic/rustic to work with