This commit makes more output properties (mode, enabled, scale and transform) atomic. This means that they are double-buffered and only applied on commit. Compositors now need to call wlr_output_commit after setting any of those properties. Internally, backends still apply properties sequentially. The behaviour should be exactly the same as before. Future commits will update some backends to take advantage of the atomic interface. Some backends are non-atomic by design, e.g. the X11 backend or the legacy DRM backend. Updates: https://github.com/swaywm/wlroots/issues/1640 |
||
---|---|---|
.. | ||
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 | ||
render.c | ||
rootston.ini.example | ||
seat.c | ||
switch.c | ||
text_input.c | ||
view.c | ||
virtual_keyboard.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
.