Skip to content

[Multi-Monitor][PerMonitorV2] ErrorProvider control is not scaled well on secondary screen #8264

@MelonWang1

Description

@MelonWang1

.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

  1. Launch VS instance on 300% primary monitor.
  2. Create a winforms .net core project.
  3. Drag and drop textbox, ErrorProvider control.
  4. 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.");
    }
  5. Build and run, input "d" to textbox control.
  6. Move to 100% secondary monitor.

Or:

  1. Extract and open errorprovider.zip on 300% primary screen.
  2. Build and run it, input "d" to textbox control.
  3. Move to 100% secondary monitor.

Actual result:
ErrorProvider control is not scaled well.
Move form 300 primary screen to 100 secondary screen:
Untitled
Move form 100 primary screen to 300 secondary screen:
Untitled1

Expected result:
ErrorProvider control should scaled well.
Move form 300 primary screen to 100 secondary screen:
100ci-normal
Move form 100 primary screen to 300 secondary screen:
300ci-normal

More Info:

  1. This issue also repro on moved VS from 100% primary to 300% secondary.
  2. This issue also repro on .NET7.0, .NET6.0.
  3. This issue not repro on framework project.
  4. This issue doesn't repro on SystemAware and DpiUnware mode.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-HDPI-PMv2Issues related to high DPI PerMonitorV2 mode

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions