Consolatis

> https://github.com/stefonarch/LXQt-Wayland-files quotes "No window rules with version 0.6, lxqt-panel not usable (manual placement)" > > Do they mean `rc.xml`'s `` Yes: https://github.com/lxqt/lxqt/issues/10#issuecomment-1426289598 I am not sure if we should...

Nice write-up. We do have an always-on-top tree for views already, we could add an always-on-bottom tree as well. So the `view` part in your list above would be split...

> preserve space (that's the most tricky, settings possible only in sway and hyprland For labwc (and possibly other compositors that support the wlr-layershell protocol) you could try something like...

In case somebody wants to experiment with layer-shell-qt: ```c++ #include #include #include #include #include int main(int argc, char **argv) { QApplication app(argc, argv); LayerShellQt::Shell::useLayerShell(); QMainWindow main_window; QPushButton button; button.setText("foobar"); main_window.setCentralWidget(&button);...

layer-shell-qt is implemented a bit different to the GTK variant from what I could see. With the GTK variant one creates a window, then give that window to a gtk-layer-shell...

> But all of its menus, tooltips and dialogs were also on the top layer and — worse than that — full-screen. Oh, I think I got that wrong, you...

On another note, it seems https://invent.kde.org/plasma/layer-shell-qt/-/merge_requests/25 that allows to have xdg-shell and layershell windows within the same application has been merged but I didn't look into it nor tested it.

We might not do mouse emulation for touch events, I don't have hardware to test this but `src/input/touch.c` is pretty small. It seems to indeed completely skip non client surfaces,...

SDDM could also just set the env vars directly before launching the compositor. I get the point about installers and live environments though.

I don't think we want to add dbus support to labwc. I agree with what @ahesford suggested above, this seems to be the best solution to the issue for me...