René D. Obermüller

Results 202 comments of René D. Obermüller

btw, would you mind closing this?

The OP issue was caused by 16aced7f9ffcac1200473192712575afaa4e6513. This added more flexibility by moving the classes from the label to the enclosing box, but it's a breaking change. I've edited the...

@crabvk since #3086 was closed as well, and you didn't see any other issues, can you close this one, please? Thanks :)

Did you have a look at commit 0ea5143? This adds the output name in env var WAYBAR_OUTPUT_NAME when you use the exec command, at first glance at least in image...

@jgarvin it does work for me with the config below. Might be a bit hard to see, but the script just echos the WAYBAR_TEST_OUTPUT on each of the screens. ![satty-20240509-21:31:27](https://github.com/Alexays/Waybar/assets/29629287/4fbfba80-0703-4c9f-9f36-f89d2941433b)...

Can you confirm whether this is still happening with recent Hyprland (e.g. 0.41.2)? wlr/taskbar depends on the wayland events being triggered. The module then doesn't do much magic with it....

Thanks for taking the time to confirm, that should be recent enough to justify further investigation ;)

I've logged into Hyprland, and I can no longer reproduce this. I'm using movetoworkspace, and the icon of the moved window is on the correct bar. Hyprland: [cc98594c3aed0b542e03818371a4636f549f80e1](https://github.com/hyprwm/Hyprland/commit/cc98594c3aed0b542e03818371a4636f549f80e1) Waybar: b26ab1f982c06ce48e96f3e4da8cde034296eb1d

I've had a look at this and at first glance I'd say there are two different issues. The first, the lack of activation, is something I cannot reproduce (anymore?) with...