mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: windows gets crazy when I quickly switch between several desktops #425
Reference in New Issue
Block a user
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?
Originally created by @tardyp on GitHub (Jun 28, 2024).
I use a lot of virtual desktops, and I switch to them pretty frequently.
When in komorebi, you switch between two desktop to heavily, komorebi gets confused and think there is an alt-tab happening.
This will eventually lead to windows getting transfered from one desktop to another.
This is especially true if some of the apps are a bit slow to redisplay their windows.
On the following video, I just switch back and forth from screen 8 to screen 9.
slowly, and then quickly
https://github.com/LGUG2Z/komorebi/assets/109859/310fa46e-d97d-451d-9ecf-dc5f4c17d83b
Eventually, all the windows from 8 and 9 end up in the same screen.
config:
komorebi log showing the reconciliations.
Would it be possible to configure a delay for reconciliation after there has been a desktop switch?
@tardyp commented on GitHub (Jun 30, 2024):
Attempting to fix the issue by playing with the reconcliation code, I ran komorebi without my own config, and realized the default config is immune to this problem.
after dumping it with komorebic generate-static-config, I realize that the problem was with
or
Only
does not exhibit this problem
@LGUG2Z commented on GitHub (Jul 1, 2024):
I think it's time to soft deprecate the Hide and Minimize options and print warnings in the next release 🤔
@tardyp commented on GitHub (Jul 1, 2024):
I don't remember exactly why I switched to minimize. The doc is a bit scary.
also, doc says
which would suggest minimize is the recommended way.
After a morning of real life use, I notice that I loose some windows when komorebi is crashing or when I restart it.
Some windows stay Cloaked, and you cannot find them neither in alt-tab or taskbar.
The only way I found is to kill the process. I don't know if you can add some sort of flags to the windows cloaked by komorebi, so that they are found and decloaked when komorebi is restarted.
Of course, you cannot decloak all windows on startup, because some might have been cloaked by another program.
@LGUG2Z commented on GitHub (Jul 1, 2024):
You should only ever stop or kill the process using the "stop" command (this also handles killing the process as a fallback); this handles uncloaking.
There is also the "restore-windows" command which can be run independently if you kill the process manually, but the list of hwnds that this reads is updated frequently so there is a good chance you'll miss your window to use this if you're trying to restart the process.