#wayland #virtual-keyboard #wayland-scanner #unstable #wayland-protocols

archived sys zwp-virtual-keyboard

DEPRECATED: (Unsafe) Rust code generated with wayland-scanner crate for virtual_keyboard_unstable_v1 protocol

1 unstable release

0.2.7 Oct 8, 2022
0.2.6 May 2, 2022
0.2.4 Sep 28, 2021
0.2.3 Jul 31, 2021
0.1.0 Sep 2, 2020

#4 in #unstable

Download history 46/week @ 2023-05-08 23/week @ 2023-05-15 19/week @ 2023-05-22 37/week @ 2023-05-29 26/week @ 2023-06-05 17/week @ 2023-06-12 43/week @ 2023-06-19 34/week @ 2023-06-26 40/week @ 2023-07-03 26/week @ 2023-07-10 27/week @ 2023-07-17 65/week @ 2023-07-24 25/week @ 2023-07-31 29/week @ 2023-08-07 36/week @ 2023-08-14 29/week @ 2023-08-21

125 downloads per month

MIT license


DEPRECATED: When I created this crate, the protocol was not available in the wayland_protocols_misc crate. Since v0.30.0-beta.10 it is available so there is no reason for this crate to continue to exits. Please use the wayland_protocols_misc crate instead.

Crate dependency status docs.rs Build dependabot status


Rust code generated with wayland-scanner crate for virtual_keyboard_unstable_v1 protocol. Some parts might not be safe, even though they are not marked ad "unsafe". One example is that you need to send the correct length of the file when sending a keymap. There might be more though.

Run the example

In order to run the example, your compositor must understand the zwp-virtual-keyboard protocol. Phosh/phoc on the Pinephone or Librem 5 understands it. I usually build the example for my Pinephone and open the editor on it. Then I use scp to copy the executable to the phone and execute it over ssh. You should now see that multiple 'x' characters are entered into the editor.

Bug with rust-analyser

Rust-analyser complains about unresolved issues, but this is a bug. It builds just fine.


PR are always welcome :)


~40K SLoC