-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
area-HDPI-PMv2Issues related to high DPI PerMonitorV2 modeIssues related to high DPI PerMonitorV2 mode
Milestone
Description
.NET version
8.0.100-alpha.1.22567.28
Did it work in .NET Framework?
Yes
Did it work in any of the earlier releases of .NET Core or .NET 5+?
No, it also repro on .NET 6.0 & 7.0.
Issue description
ErrorProvider control is not scaled well in secondary screen under PermonitorV2 mode.
Steps to reproduce
- Launch VS instance on 300% primary monitor.
- Create a winforms .net core project.
- Drag and drop textbox, ErrorProvider control.
- Double click textbox control and add below code:
try
{
int x = Int32.Parse(textBox1.Text);
errorProvider1.SetError(textBox1, "");
}
catch (Exception ex)
{
errorProvider1.SetError(textBox1, "Not an integer value.");
} - Build and run, input "d" to textbox control.
- Move to 100% secondary monitor.
Or:
- Extract and open errorprovider.zip on 300% primary screen.
- Build and run it, input "d" to textbox control.
- Move to 100% secondary monitor.
Actual result:
ErrorProvider control is not scaled well.
Move form 300 primary screen to 100 secondary screen:
Move form 100 primary screen to 300 secondary screen:
Expected result:
ErrorProvider control should scaled well.
Move form 300 primary screen to 100 secondary screen:
Move form 100 primary screen to 300 secondary screen:
More Info:
- This issue also repro on moved VS from 100% primary to 300% secondary.
- This issue also repro on .NET7.0, .NET6.0.
- This issue not repro on framework project.
- This issue doesn't repro on SystemAware and DpiUnware mode.
Metadata
Metadata
Assignees
Labels
area-HDPI-PMv2Issues related to high DPI PerMonitorV2 modeIssues related to high DPI PerMonitorV2 mode