mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Tile sizes are incorrect with different windows scaling #275
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 @Alan-Manning on GitHub (Jan 2, 2024).
Describe the bug
If i have my monitor with display scaling on the windows do not have the correct size when switching between monitors. This does not happen when the display is set to scale 100% but i use a 125% on my main. This is resolved when switching on that same monitor, it is only switching between monitors. Also this only happends with some things like chrome ( as i show in the vids below ).
To Reproduce
Steps to reproduce the behavior:
have two or more monitors with a different scaling between them.

Switch the tile across those monitors.
See bug.
Move that incorrectly sized tile around that same monitor to fix.
No longer see bug.
Expected behavior
Should just respect the scale of the monitor when initially deciding the size of that tile on the new window.
Screenshots and Videos
I have the videos below showing chrome switching between the monitors on 100% scaling and 125% scaling.
First is the 100 Scaling.
https://github.com/LGUG2Z/komorebi/assets/110160546/67655f6d-058d-475a-be21-9e7d7e779731
Then the 125% Scaling
https://github.com/LGUG2Z/komorebi/assets/110160546/f8a8a056-7294-4727-80e8-c8f0b886e3db
Operating System
OS Name: Microsoft Windows 11 Pro N
Version: 10.0.22631 Build 22631
komorebic checkOutputNo 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.
@LGUG2Z commented on GitHub (Jan 6, 2024):
This is now fixed on
masterand will be part of the next release! 🎉