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

sys zwp-virtual-keyboard

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

5 releases

new 0.2.3 Jul 31, 2021
0.2.2 Feb 13, 2021
0.2.1 Feb 13, 2021
0.2.0 Sep 26, 2020
0.1.0 Sep 2, 2020

#218 in GUI

Download history 153/week @ 2021-04-12 54/week @ 2021-04-19 65/week @ 2021-04-26 36/week @ 2021-05-03 34/week @ 2021-05-10 23/week @ 2021-05-17 23/week @ 2021-05-24 23/week @ 2021-05-31 33/week @ 2021-06-07 25/week @ 2021-06-14 26/week @ 2021-06-21 70/week @ 2021-06-28 22/week @ 2021-07-05 9/week @ 2021-07-12 21/week @ 2021-07-19 33/week @ 2021-07-26

120 downloads per month
Used in zwp-input-method-service

MIT license

18KB

Crate dependency status Build

zwp-virtual-keyboard

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.

Contributing

PR are always welcome :)

Dependencies

~1.5MB
~31K SLoC