-
-
Notifications
You must be signed in to change notification settings - Fork 755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hyprland: Special workspace switching is wonky #2861
Comments
Hey there! It's a combination of problems: originally, some Hyprland IPC messages would purposefully not include the I'm working on a solution in #2864. Although the first commit already addresses this problem, I'm thinking of implementing a wrapper type for the name attribute so that you can't compare just names (think of Rust enums). I'll see where that gets me. For the time, could you please try that PR, @Jaques22 ? |
Amazing thanks that PR fixes the issues i was having. Special workspaces now show up like i'd expect. |
Oh that's not a problem caused specifically because your special and regular workspaces share the same name, that's just a thing in waybar. If I'm not mistaken either Hyprland doesn't notify when the special is toggled or we are not listening to the right event (can't remember). I'll check later to see which is it and, if the latter, I'll implement it |
Switching between two empty workspaces fast, causes undesired glitch effect, because the both of them are visible for a short time, until the one is cleared. Note this does not happen under sway, only in hyprland. |
This sounds like a completely different issue. I'd open a separate bug report if I were you. |
You're probably encountering this issue: #2484 |
I have hyprland/workspaces module loaded in waybar and i have noticed that if i open an empty special workspace and then close it again, the regular workspace with the same number is removed from waybar.
Steps to reproduce:
Have hyprland/workspaces loaded into waybar
On workspace 1, open workspace
special:1
using a defined key bind.Close that special workspace with no windows on it.
Notice that the waybar workspaces module is now missing workspace 1.
I have repro'd this issue after running
socat - UNIX-CONNECT:/tmp/hypr/$HYPRLAND_INSTANCE_SIGNATURE/.socket2.sock
and got this output:To me (not a programmer), it looks like it's because the hyprland socket doesn't report that workspace 1 is focused again after the special is closed. Only reporting the focused window, in my case kitty.
I initially thought this was a hyprland issue but after the above steps, switching between regular workspaces never brings back the one that "disappeared" on waybar despite hyprland correctly reporting the workspace switch.
Hope this made sense, if you need any more info/testing I'm happy to help!
The text was updated successfully, but these errors were encountered: