JakeStanger/ironbar

If running another compositor like sway on another tty, and then exiting the main compositor on tty1 (in my case niri) relaunching the compositor leads to the workspace module showing nothing. Note that on sway I'm not using ironbar, but somehow launching sway breaks something in the ipc communication. To reproduce I have found a reliable way to replicate this: Launch niri and ironbar on tty1, workspace module works fine Launch sway on tty2 Go back to tty1, exit niri Launch niri again: the workspace module is now broken. My assumption is that ironbar tries connecting to sway's ipc socket instead of niri At this point something strange happens: if I quit both sway on tty2 and niri on tty1 and relaunch niri I expect to have a "fresh start", but instead the workspace module is still broken and shows failed to create module Workspaces: 0: File o directory non esistente (os error 2) So I believe that instead of "cleanly" reconnecting to the new niri socket ironbar tries connecting t

Is your feature request related to a problem? Please describe. I'd just like to be able to hover over certain modules to reveal other ones a la groups Describe the solution you'd like https://github.com/Alexays/Waybar/wiki/Module:-Group feels like it just makes sense and would be a relatively simple module to add, I use it to hide a bunch of my smaller rarely used modules behind a commonly used one I also use it to reveal the names of things on hover, such as if I hover on my bluetooth module it shows the currently connected devices, my volume one also hides a slider until I hover, saves a click. i think a simple way to add this would be to allow show_if to detect a hover event maybe?