-
Notifications
You must be signed in to change notification settings - Fork 975
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
[Multi-Monitor] PerMonitorV2 autoscale lead to wrong ClientSize. #12132
Comments
@Olina-Zhang could you please find what PR in NET8 had regressed this behavior and if the quirks can help with this issue. |
This is not regression from .Net6 (may be earlier?):
|
@kirsan31 - we want to see what caused the bigger difference. |
@Tanya-Solyanik This behavior is regression from: #7973 and here are the test results. test12132.mp4 |
Sorry but I still don't get why you call this regression. 🤷♂️ In .Net 8 it's become more accurate then before, but still not 100% accurate.
|
One question: why the correct size on 125% is 715x644 based on 100%: 626x483, not 783x604 on 125%? |
@Olina-Zhang All my previous conclusions was made comparing to systemaware scaling and in this terms .Net8 PerMonitorV2 more close to it than .Net5-7. |
642 * 1.25 = 802.5 |
Yea I already got it - explained in my previous post above (I couldn't imagine that systemaware scaling is wrong). |
.NET version
8.0.7
Did it work in .NET Framework?
No.
Did it work in any of the earlier releases of .NET Core or .NET 5+?
.Net 5 - 7 have similar problem but the difference is match smaller.
Can't test 9.0RC1 due to build error:
Issue description
PerMonitorV2
app.ClientSize = CLS1
. The same as launchSystemAware
app.ClientSize = CLS2
.And
CLS1 != CLS2
.Steps to reproduce
WinFormsPerMonitorV2.zip
ClientSize
values.or
ClientSize
values.The text was updated successfully, but these errors were encountered: