You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling Pause Mode (alt+shift+p) you are not able to use any of the key combinations tied to GlazeWM for another application. Then also when you disable Pause Mode those commands run as if it was queued.
Reproduction
Open Windows Calculator
Enable Pause Mode (alt+shift+p)
Hit alt+3
Expected behavior: Calculator enters Graph Mode
Actual behavior: Nothing happens
Exit Pause Mode (alt+shift+p)
Expected behavior: Nothing happens
Actual behavior: Switches to workspace 3
Stack trace or error logs (if applicable)
No response
Version number
3.7.0
The text was updated successfully, but these errors were encountered:
Hey @ShortArrow I don't see that pause button on the status bar. Just this:
I use Windows 11 Pro 23H2 and I'm on version 3.7.0
@reesebiz
Your shortcut key shift-alt-p may not be activated pause mode.
Please check if the following output is present in the glazewm log.
If it is not present, the shortcut key may have been overwritten by another app.
2024-12-19T00:29:37.115261Z INFO glazewm: Received WM event: BindingModesChanged { new_binding_modes: [BindingModeConfig { name: "pause", display_name: None, keybindings: [KeybindingConfig { bindings: ["alt+shift+p"], commands: [WmDisableBindingMode { name: "pause" }] }] }] }
2024-12-19T00:29:37.297427Z INFO glazewm: Received WM event: BindingModesChanged { new_binding_modes: [] }
Describe the bug
When enabling Pause Mode (alt+shift+p) you are not able to use any of the key combinations tied to GlazeWM for another application. Then also when you disable Pause Mode those commands run as if it was queued.
Reproduction
Expected behavior: Calculator enters Graph Mode
Actual behavior: Nothing happens
Expected behavior: Nothing happens
Actual behavior: Switches to workspace 3
Stack trace or error logs (if applicable)
No response
Version number
3.7.0
The text was updated successfully, but these errors were encountered: