-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application window grows each time it's run #393
Comments
If it was solely related to scaling, I would expect larger changes. These changes seem to be more related to borders and titlebar in conjunction with scaling. It as probably something in whatever size gets reported and how the app initializes. It can be very dependent on the OS and whatever window theming and customizations you have, so I would at least need additional information to be able to even look into this. You can also disable scaling temporarily to see if the issue persists. |
another though is that it could be caused if the screens are not properly aligned. |
I'm using four monitors in the following configuration:
Top> 1600x1200 (4:3) @100% scaling
Left> 1920x1200 (8:5) @100% scaling
Middle> 3840x2160 (16:9) @150% scaling
Right> 1920x1200 (8:5) @100% scaling
I thought EDOMH was "forgetting" it's window position due to this setup. Now I've realized it's actually increasing it's size down and right on every launch. It does this consistently on all except my middle monitor. It retains it's correct size on every launch on that one.
I took screenshots of three successive launches on the right monitor, and opened them in my graphics editor. Upon zooming in for exact coordinates, I found the following pixel locations:
1> Left= 5788, Top= 1259, Right= 7651, Bottom= 2365
2> Left= 5788, Top= 1259, Right= 7657, Bottom= 2382
3> Left= 5788, Top= 1259, Right= 7663, Bottom= 2399
It's increasing it's width by 6 pixels to the right, and it's height by 17 pixels downward. The window eventually ends up with it's right and bottom edges off the monitor because of this.
I'm guessing this is somehow related to either the differences in scaling and/or the aspect ratios. I'd appreciate a fix if possible, but this is not a critical issue. I've been seeing this since version 2.21 (now on 2.89), so I'm used to it.
The text was updated successfully, but these errors were encountered: