dotnet / dotnet/winforms

[Multi-Monitor] PictureBox don't scale well on the secondary monitor when application is in PerMonitorV2 mode

Open
#9,249 1 comment 0 reactions 0 assignees View on GitHub
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.23307.24

### Did it work in .NET Framework?

No

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

No, it doesn't work in .NET 6.0/7.0/8.0, not a regression issue.

### Issue description

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

https://github.com/dotnet/winforms/assets/86937911/a1d2f5d6-accc-4e20-9ca2-236d2bdc0eb3

100%DPI:

![picturebox100](https://github.com/dotnet/winforms/assets/86937911/218455b2-df12-4c55-8bcf-ea7f8d6c2e07)

100% primary monitor -> 300% secondary monitor:

![picturebox300](https://github.com/dotnet/winforms/assets/86937911/cfefd915-4d20-453a-b240-890bb91157e0)

This issue also repro's when move from 300% primary monitor to 100% secondary monitor.

https://github.com/dotnet/winforms/assets/86937911/84d21b90-ceea-4282-9794-7f1ce1acee36

This issue also repro's on design time.

https://github.com/dotnet/winforms/assets/86937911/47a42df1-b8ed-4a4d-80db-622c3b32f05a

### Steps to reproduce

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

**More Info:**

1. This issue also repro's on design time.
2. This issue also repro's when move from 300% primary monitor to 100% secondary monitor.
3. This issue only repro on `PerMonitorV2`application mode.

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.