5de26ad8ed
Frame events group logically connected pointer events. It makes sense to make the backend responsible for sending frame events, since once the events are split (ie. once the frame events are stripped) it's not easy to figure out which events belongs to which frame again. This is also how Weston handles frame events. Fixes https://github.com/swaywm/wlroots/issues/1468 |
||
|---|---|---|
| .. | ||
| README.md | ||
| bindings.c | ||
| config.c | ||
| cursor.c | ||
| desktop.c | ||
| ini.c | ||
| input.c | ||
| keyboard.c | ||
| layer_shell.c | ||
| main.c | ||
| meson.build | ||
| output.c | ||
| rootston.ini.example | ||
| seat.c | ||
| switch.c | ||
| text_input.c | ||
| virtual_keyboard.c | ||
| wl_shell.c | ||
| xdg_shell.c | ||
| xdg_shell_v6.c | ||
| xwayland.c | ||
README.md
rootston
Rootston is the "big" wlroots test compositor. It implements basically every feature of wlroots and may be useful as a reference for new compositors. However, it's mostly used as a testbed for wlroots development and does not have particularly clean code and is not particularly well designed: proceed with a grain of salt. It is not designed for end-users.
Running rootston
If you followed the build instructions in ../README.md, the rootston
executable can be found at build/rootston/rootston. To use it, refer to the
example config at rootston/rootston.ini.example and place a
config file of your own at rootston.ini in the working directory (or in an
arbitrary location via rootston -C). Other options are available, refer to
rootston -h.