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
Zebar has excess of shown info and takes a space on the screen (especially for 13' laptops). Most of the shown data can me dublicated in Windows Taskbar except current workspace.
Describe the solution you'd like
Get simple tray indicator to show current workspace (and probably pause state) similar to komorebit
Alternatives considered
At list make a separate CLI command for getting current active workspace and pause/unpause state, it could be possible to make simple alternative app on any other language than messing around with glazewm npm package.
The text was updated successfully, but these errors were encountered:
i think this is a good idea for people that still want to use the taskbar, having the taskbar plus Zebar is kinda annoying, plus the taskbar is more functional than Zebar, and autohide is just bad.
maybe a lightweight app that shows workspaces in the system tray?
made simple tray utility glazetray. Shows only active workspace (up to 10) for workspaces with default names ("1", "2", "3" ...) and single monitor setup.
made simple tray utility glazetray. Shows only active workspace (up to 10) for workspaces with default names ("1", "2", "3" ...) and single monitor setup.
Can a feature be added that also shows the tiling direction along with the workspace number.
Thanks
Describe the problem/motivation
Zebar has excess of shown info and takes a space on the screen (especially for 13' laptops). Most of the shown data can me dublicated in Windows Taskbar except current workspace.
Describe the solution you'd like
Get simple tray indicator to show current workspace (and probably pause state) similar to komorebit
Alternatives considered
At list make a separate CLI command for getting current active workspace and pause/unpause state, it could be possible to make simple alternative app on any other language than messing around with glazewm npm package.
The text was updated successfully, but these errors were encountered: