Also I forgot to mention that I have made a wee script that counts how many screens are connected and deploys yambar to how ever many there are. I even have it working with #Kanshi so you can change screens on the fly.

Right now we're cooking !
I've canned #Waybar and have successfully gotten #Yambar configured and running via #Kanshi . This allows me to undock my laptop and Kanshi will run my script that counts how many screens are connected and kills or starts the relevant Yambar on each screen.
Now to start customising the bar to my liking and maybe witting another couple of scripts for it too.
#River #RiverWm #Wayland #Linux

#Shikane
A dynamic output configuration tool that automatically detects and configures
connected outputs based on a set of profiles.
This is a #Wayland equivalent for tools like autorandr.
It aims to fully replace #kanshi and add new features.
shikane works with Wayland compositors supporting version 3 of the
wlr-output-management protocol (e.g., compositors using #wlroots v0.16).
https://gitlab.com/w0lff/shikane

It's looking more and more like I'll be switching full time to #Hyprland as I've been able to do more than I could with my :heart: #qtile and also being able to run #Ardour without issue for my home studio setup is really important to me too. I've managed to get everything just as I like it using #EwwBar and I don't even need #Kanshi anymore. I have a dual screen setup that does everything that I need from it and it took a while to workout what I needed to do code wise but it works for me.

Boost got my #EwwBar / #Hyprland custom workspace and dispatcher scripts working on my dual screen setup and they still work on a single too if the external screen is unplugged. Only issue left to sort is when the external is plugged back in that screens bar is gone. So I'll have to use a hook for detecting the screen being reconnected and make sure the bar restarts then hopefully job done. I'm trying to avoid having to use #Kanshi if it can be helped.
#ArchLinux