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
What is the request?.
To add a way to specify which monitor/screen the komorebi widgets should show information for and control, so that the widgets can be used for screens other than the screen the bar is on.
Why is it useful?
I use komorebi with a dual-monitor setup. Since my primary monitor is an OLED and I want to avoid static elements on it, I use yasb only on the secondary monitor. It would be amazing to be able to have komorebi workspace/layout indicators for both monitors on that bar.
How could it be implemented?
For example, by adding an optional screen_index to the widget configuration. If omitted, the widget would target the screen the bar is on (the current behaviour), but you could set this to override the screen it targets.
Additional context
This seems like a fairly straightforward feature to implement, so let me know if you'd like me to file a pull request for it :)
The text was updated successfully, but these errors were encountered:
What is the request?.
To add a way to specify which monitor/screen the komorebi widgets should show information for and control, so that the widgets can be used for screens other than the screen the bar is on.
Why is it useful?
I use komorebi with a dual-monitor setup. Since my primary monitor is an OLED and I want to avoid static elements on it, I use yasb only on the secondary monitor. It would be amazing to be able to have komorebi workspace/layout indicators for both monitors on that bar.
How could it be implemented?
For example, by adding an optional
screen_index
to the widget configuration. If omitted, the widget would target the screen the bar is on (the current behaviour), but you could set this to override the screen it targets.Additional context
This seems like a fairly straightforward feature to implement, so let me know if you'd like me to file a pull request for it :)
The text was updated successfully, but these errors were encountered: