Originally created by @Fuann-Kinoko on GitHub (May 10, 2023).
Originally assigned to: @LGUG2Z on GitHub.
Describe the bug
When switching from one workspace to another, if there is only one single window in one of the workspaces, then the active-window-border-colour for monocle-kind does not change correctly
To Reproduce
Incorrect behavior 1:
Assume workspace 1 has only 1 window, while workspace 2 has 2 windows.
Enter monocle layout in workspace 2, which changes the color of border.
Switch to workspace 1, the border color changes to the normal color, which is correct.
Then switch back to workspace 2, however, the border color does not change to the "monocle color".
Incorrect behavior 2:
Assume workspace 1 has only 1 window, while workspace 2 has 2 windows.
Enter monocle layout in workspace 1, which won't change the color since there's only one window.
Switch to workspace 2, everything's fine.
Then switch back to workspace 1, the border disappears.
Expected behavior
active-window-border-colour for monocle updates seperately and correctly for different workspaces, according to the current workspace layout.
Operating System
OS Name: Microsoft Windows 10
OS Version: 10.0.19044 N/A Build 19044
Originally created by @Fuann-Kinoko on GitHub (May 10, 2023).
Originally assigned to: @LGUG2Z on GitHub.
**Describe the bug**
When switching from one workspace to another, if there is only one single window in one of the workspaces, then the active-window-border-colour for monocle-kind does not change correctly
**To Reproduce**
Incorrect behavior 1:
1. Assume `workspace 1` has only 1 window, while `workspace 2` has 2 windows.
2. Enter monocle layout in `workspace 2`, which changes the color of border.
3. Switch to `workspace 1`, the border color changes to the normal color, which is correct.
4. Then switch back to `workspace 2`, however, the border color does not change to the "monocle color".
Incorrect behavior 2:
1. Assume `workspace 1` has only 1 window, while `workspace 2` has 2 windows.
2. Enter monocle layout in `workspace 1`, which won't change the color since there's only one window.
3. Switch to `workspace 2`, everything's fine.
4. Then switch back to `workspace 1`, the border disappears.
**Expected behavior**
active-window-border-colour for monocle updates seperately and correctly for different workspaces, according to the current workspace layout.
**Operating System**
```
OS Name: Microsoft Windows 10
OS Version: 10.0.19044 N/A Build 19044
```
adam
added the bug label 2026-01-05 14:48:59 +01:00
@LGUG2Z commented on GitHub (Jan 15, 2024):
This was recently fixed on master and will be in the next release, forgot to link it to this issue!
fix commit: https://github.com/LGUG2Z/komorebi/commit/5a6dcef7eaede5815318e7821121fd8476e3287f
video: https://www.youtube.com/watch?v=WiUVRRKHD4k
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Fuann-Kinoko on GitHub (May 10, 2023).
Originally assigned to: @LGUG2Z on GitHub.
Describe the bug
When switching from one workspace to another, if there is only one single window in one of the workspaces, then the active-window-border-colour for monocle-kind does not change correctly
To Reproduce
Incorrect behavior 1:
workspace 1has only 1 window, whileworkspace 2has 2 windows.workspace 2, which changes the color of border.workspace 1, the border color changes to the normal color, which is correct.workspace 2, however, the border color does not change to the "monocle color".Incorrect behavior 2:
workspace 1has only 1 window, whileworkspace 2has 2 windows.workspace 1, which won't change the color since there's only one window.workspace 2, everything's fine.workspace 1, the border disappears.Expected behavior
active-window-border-colour for monocle updates seperately and correctly for different workspaces, according to the current workspace layout.
Operating System
@LGUG2Z commented on GitHub (May 10, 2023):
Reproduced
@NathanealV commented on GitHub (Jan 15, 2024):
I've also noticed this issue when using Komorebi - have there been any updates on this?
@LGUG2Z commented on GitHub (Jan 15, 2024):
This was recently fixed on master and will be in the next release, forgot to link it to this issue!
fix commit: https://github.com/LGUG2Z/komorebi/commit/5a6dcef7eaede5815318e7821121fd8476e3287f
video: https://www.youtube.com/watch?v=WiUVRRKHD4k