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

Switching Windows virtual desktops breaks layout #13

New Issue
Closed
opened 2026-01-05 14:47:39 +01:00 by adam · 4 comments
adam commented 2026-01-05 14:47:39 +01:00
Owner
Copy Link

Originally created by @naoey on GitHub (Aug 19, 2021).

Originally assigned to: @LGUG2Z on GitHub.

Tiling works perfectly on starting komorebi up but windows get smaller and smaller each time I switch to and from other virtual desktops. In some cases its just one window that's affected in some cases its all the windows on that virtual desktop. I haven't been able to identify a pattern to it so far.

Unsure if its once again related to me having a multi-monitor configuration. I use:

  • 2560x1440 primary
  • 3840x2160 (scaled to 2560x1440) secondary

This is occurring both when using the pre-built release as well as when building it myself on 98f731b.

image

Originally created by @naoey on GitHub (Aug 19, 2021). Originally assigned to: @LGUG2Z on GitHub. Tiling works perfectly on starting komorebi up but windows get smaller and smaller each time I switch to and from other virtual desktops. In some cases its just one window that's affected in some cases its all the windows on that virtual desktop. I haven't been able to identify a pattern to it so far. Unsure if its once again related to me having a multi-monitor configuration. I use: - 2560x1440 primary - 3840x2160 (scaled to 2560x1440) secondary This is occurring both when using the pre-built release as well as when building it myself on 98f731b. ![image](https://user-images.githubusercontent.com/3889501/129996780-8d0385b1-7693-4e5b-9741-e9a0632ddfef.png)
adam added the bug label 2026-01-05 14:47:39 +01:00
adam closed this issue 2026-01-05 14:47:39 +01:00
adam commented 2026-01-05 14:47:40 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Aug 19, 2021):

@naoey Can you confirm that this is happening when switching between the native Windows Virtual Desktops and not komorebi's implementation of workspaces?

If this is happening with komorebi's implementation of workspaces it is definitely a bug and it would help if you could record a video of this happening so that I can try to accurately reproduce it.

komorebi generally doesn't aim for compatibility with Windows Virtual Desktops, because the public API is extremely lacking. In fact, it is the lack of stability around advanced programmatic access to Windows Virtual Desktops that led me to create a completely independent workspaces implementation for komorebi.

Nevertheless, I would be tempted to at least try to fix this specific bug, because the fix would help to ensure that while komorebi doesn't provide compatibility and interoperability with Windows Virtual Desktops, it also does not permit Windows Virtual Desktops to introduce weird/undefined/breaking behaviour into the komorebi process.

@LGUG2Z commented on GitHub (Aug 19, 2021): @naoey Can you confirm that this is happening when switching between the native Windows Virtual Desktops and not `komorebi`'s implementation of workspaces? If this is happening with `komorebi`'s implementation of workspaces it is definitely a bug and it would help if you could record a video of this happening so that I can try to accurately reproduce it. `komorebi` generally doesn't aim for compatibility with Windows Virtual Desktops, because [the public API](https://docs.microsoft.com/en-us/windows/win32/api/shobjidl_core/nn-shobjidl_core-ivirtualdesktopmanager) [is extremely lacking](https://docs.microsoft.com/en-us/archive/blogs/winsdk/virtual-desktop-switching-in-windows-10). In fact, it is [the lack of stability around advanced programmatic access to Windows Virtual Desktops](https://github.com/Ciantic/VirtualDesktopAccessor/issues/33) that led me to create a completely independent workspaces implementation for `komorebi`. Nevertheless, I would be tempted to at least try to fix this specific bug, because the fix would help to ensure that while `komorebi` doesn't provide compatibility and interoperability with Windows Virtual Desktops, it also does not permit Windows Virtual Desktops to introduce weird/undefined/breaking behaviour into the `komorebi` process.
adam commented 2026-01-05 14:47:40 +01:00
Author
Owner
Copy Link

@naoey commented on GitHub (Aug 19, 2021):

Yes, sorry if that wasn't clear. I did mean this is occurring with Windows Virtual Desktops.

komorebi generally doesn't aim for compatibility with Windows Virtual Desktops, because the public API is extremely lacking

That's completely understandable. I'm somewhat accustomed to using them as the Windows equivalent of Spaces on macOS so even if not feasible to get the same level of compatibility as yabai provides, just having it not disrupt the layout would be great!

@naoey commented on GitHub (Aug 19, 2021): Yes, sorry if that wasn't clear. I did mean this is occurring with Windows Virtual Desktops. > komorebi generally doesn't aim for compatibility with Windows Virtual Desktops, because the public API is extremely lacking That's completely understandable. I'm somewhat accustomed to using them as the Windows equivalent of Spaces on macOS so even if not feasible to get the same level of compatibility as yabai provides, just having it not disrupt the layout would be great!
adam commented 2026-01-05 14:47:40 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Aug 19, 2021):

@naoey I have made some changes that limit the komorebi listeners to the Windows Virtual Desktop that the process was started from. In practice, this means that you can have a single Virtual Desktop which runs komorebi with komorebi's implementation of workspaces, and other Virtual Desktops that know nothing about komorebi and which komorebi knows nothing about. 👌

@LGUG2Z commented on GitHub (Aug 19, 2021): @naoey I have made some changes that limit the `komorebi` listeners to the Windows Virtual Desktop that the process was started from. In practice, this means that you can have a single Virtual Desktop which runs `komorebi` with `komorebi`'s implementation of workspaces, and other Virtual Desktops that know nothing about `komorebi` and which `komorebi` knows nothing about. 👌
adam commented 2026-01-05 14:47:40 +01:00
Author
Owner
Copy Link

@es183923 commented on GitHub (Aug 2, 2022):

Looks like this still is happening when switching between windows' virtual desktops when building from master a6d46dbf45.

Komorebi seems to forget that windows were minimized, and results in it allocating space for minimized windows, which it shouldn't.

@es183923 commented on GitHub (Aug 2, 2022): Looks like this still is happening when switching between windows' virtual desktops when building from master a6d46dbf450012239637e92430553d5957fd051c. Komorebi seems to forget that windows were minimized, and results in it allocating space for minimized windows, which it shouldn't.
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#13
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?