dotnet / dotnet/winforms

RadioButton and CheckBox are not scaled well on the secondary monitor when application is in PerMonitorV2 mode

Open
#9,200 9 comments 0 reactions 0 assignees View on GitHub
:boom: regression-release area-HDPI-PMv2
Dominant language
C#
Stars
4.9k
Forks
1.1k
Avg merge
20h 23m
Merged PRs (30d)
103

Description

### .NET version

.NET 8.0.100-preview.6.23280.13

### Did it work in .NET Framework?

Yes

### Did it work in any of the earlier releases of .NET Core or .NET 5+?

Yes, it works in .NET 6.0/7.0/8.0.100-preview.5.23262.2, doesn't work in 8.0.100-preview.5.23268.15.

### Issue description

Testapp: [Testapp.zip](https://github.com/dotnet/winforms/files/11610888/Testapp.zip)

https://github.com/dotnet/winforms/assets/86937911/6d4d445c-930f-4d03-a3ea-a439026670e4

100%DPI:
![image](https://github.com/dotnet/winforms/assets/86937911/90271b0a-36b3-429c-b9c5-f8addb2415a7)
100% primary monitor -> 300% secondary monitor
![image](https://github.com/dotnet/winforms/assets/86937911/21d1b47f-0652-4efd-af8c-ac845b901bc9)
300%DPI:
![image](https://github.com/dotnet/winforms/assets/86937911/ed038478-6b3d-4b4c-b55e-30c498e2fa6a)
300% primary monitor -> 100% secondary monitor
![image](https://github.com/dotnet/winforms/assets/86937911/2aa9e800-7a06-4674-9351-8b74c502529e)

### Steps to reproduce

1. Launch VS instance on 100% primary monitor.
2. Add `PerMonitorV2` in csproj file.
3. Close and reopen Solution.
4. Add some radioButton and checkBox controls to form designer.
5. Build and run the application.
6. Move to 300% secondary monitor.

**More Info:**
1. This issue does not happen at design time.
2. This issue only repro on radiobutton and checkbox control.
3. This issue also occurs when move from 300% primary monitor to 100% secondary monitor.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.