starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: Border Colours are incorrect upon switching #274

New Issue
Closed
opened 2026-01-05 14:49:25 +01:00 by adam · 2 comments
adam commented 2026-01-05 14:49:25 +01:00
Owner
Copy Link

Originally created by @Alan-Manning on GitHub (Jan 2, 2024).

Describe the bug
When you set a window to be monocle or stack the border color changes correctly however when i switch to another window and then back to that stack or monocle then the border colour is incorrect and is just the regular single colour. And when i unstack or unmonocle this after it being the wrong colour makes the single colour incorrect. This makes determining what windows are where tricky. ive shown a few images below with the terminal with trasnparent bg to more clearly show this.

To Reproduce
Steps to reproduce the behavior:

  1. open window into monocle mode ( or stack some windows together ).
  2. switch to another window on another screen ( or switch to window that isnt stacked on same screen ).
  3. switch back to the monocle window ( or back to the stack ).
  4. The window border is wrong color - the single border colour.
  5. Switching back to the normal single mode again will then show the incorrect colour ( that being the colour it should have been when i switched back to it initally ).

Expected behavior
It should be the same colour as when i left it. whether that be stack of monocle colours. and be single colours when i toggle out of those modes.

Screenshots and Videos
This is an initial proper border colour.
gVpQZnQT0x

This is the terminal set to monocle.
SxNzpYkalV

This is the terminal again after switching away and back again.
6dlnMAJGxz

This is the terminal again after switching out of monocle mode.
BEYZSfSVl0

Operating System
OS Name: Microsoft Windows 11 Pro N
Version: 10.0.22631 Build 22631

komorebic check Output

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Alan_

Looking for configuration files in C:\Users\Alan_

No komorebi configuration found in C:\Users\Alan_

If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration

Additional context
Dont think there is anythong else i can add to clarify.

Originally created by @Alan-Manning on GitHub (Jan 2, 2024). **Describe the bug** When you set a window to be monocle or stack the border color changes correctly however when i switch to another window and then back to that stack or monocle then the border colour is incorrect and is just the regular single colour. And when i unstack or unmonocle this after it being the wrong colour makes the single colour incorrect. This makes determining what windows are where tricky. ive shown a few images below with the terminal with trasnparent bg to more clearly show this. **To Reproduce** Steps to reproduce the behavior: 1. open window into monocle mode ( or stack some windows together ). 2. switch to another window on another screen ( or switch to window that isnt stacked on same screen ). 3. switch back to the monocle window ( or back to the stack ). 4. The window border is wrong color - the single border colour. 5. Switching back to the normal single mode again will then show the incorrect colour ( that being the colour it should have been when i switched back to it initally ). **Expected behavior** It should be the same colour as when i left it. whether that be stack of monocle colours. and be single colours when i toggle out of those modes. **Screenshots and Videos** This is an initial proper border colour. ![gVpQZnQT0x](https://github.com/LGUG2Z/komorebi/assets/110160546/aac21db4-d26e-4828-a667-9d3317489612) This is the terminal set to monocle. ![SxNzpYkalV](https://github.com/LGUG2Z/komorebi/assets/110160546/7301fd48-3f07-4c38-829d-27f00189c8e1) This is the terminal again after switching away and back again. ![6dlnMAJGxz](https://github.com/LGUG2Z/komorebi/assets/110160546/028b6672-7eaf-488a-a116-c26755b239a9) This is the terminal again after switching out of monocle mode. ![BEYZSfSVl0](https://github.com/LGUG2Z/komorebi/assets/110160546/742e0d78-d827-4de1-bbb0-b80beb7c7ca4) **Operating System** OS Name: Microsoft Windows 11 Pro N Version: 10.0.22631 Build 22631 **`komorebic check` Output** No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Alan_ Looking for configuration files in C:\Users\Alan_ No komorebi configuration found in C:\Users\Alan_ If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration **Additional context** Dont think there is anythong else i can add to clarify.
adam added the bug label 2026-01-05 14:49:25 +01:00
adam closed this issue 2026-01-05 14:49:25 +01:00
adam commented 2026-01-05 14:49:26 +01:00
Author
Owner
Copy Link

@cubeDHS2017 commented on GitHub (Jan 2, 2024):

This also happens to me when I switch work space sometimes.

@cubeDHS2017 commented on GitHub (Jan 2, 2024): This also happens to me when I switch work space sometimes.
adam commented 2026-01-05 14:49:26 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 15, 2024):

Live video of this being fixed here: https://www.youtube.com/watch?v=WiUVRRKHD4k

@LGUG2Z commented on GitHub (Jan 15, 2024): Live video of this being fixed here: https://www.youtube.com/watch?v=WiUVRRKHD4k
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#274
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?