Skip to content

Conversation

LeafShi1
Copy link
Member

@LeafShi1 LeafShi1 commented Mar 5, 2025

BackPort PR #12947 to 9.0
Fixes #12939

Proposed changes

  • Calculate the display size of the ErrorProvide Icon according to the DPI of the current device

Customer Impact

  • The icon of errorProvider is not scaled well on HDPI screen

Regression?

Risk

  • Low – because the change only change ErrorProvider icon's display size when it run in HDPI screen.

Testing

  • Manual testing with the user-provided project
Microsoft Reviewers: Open in CodeFlow

<!-- Please read CONTRIBUTING.md before submitting a pull request -->

Fixes dotnet#12939

## Proposed changes

- Scale errorProvider Icon to DeviceDPI

<!-- We are in TELL-MODE the following section must be completed -->

## Customer Impact

- The icon of errorProvider can be scaled well on HDPI screen

## Regression?

- Yes

## Risk

- Minimal

<!-- end TELL-MODE -->

## Screenshots <!-- Remove this section if PR does not change UI -->

### Before
The icon of errorProvider is not scaled well on HDPI screen with
SystemAware and PerMoniterV2 modes

![BeforeChange](https://github.com/user-attachments/assets/bf20fcc8-bc09-44f3-b9c4-9fb1beb4751c)

### After
The icon of errorProvider can be scaled well on HDPI screen

![AfterChange](https://github.com/user-attachments/assets/c757eb70-9bee-4114-a2a5-55dc7a34fb2b)

## Test methodology <!-- How did you ensure quality? -->

- Manually

## Test environment(s) <!-- Remove any that don't apply -->

- .net 10.0.0-preview.2.25111.15

<!-- Mention language, UI scaling, or anything else that might be
relevant -->

###### Microsoft Reviewers: [Open in
CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/dotnet/winforms/pull/12947)
Copy link

codecov bot commented Mar 5, 2025

Codecov Report

Attention: Patch coverage is 76.47059% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.84325%. Comparing base (44f90e2) to head (2837ea3).
Report is 4 commits behind head on release/9.0.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           release/9.0      #13079         +/-   ##
=====================================================
+ Coverage     74.83821%   74.84325%   +0.00503%     
=====================================================
  Files             3022        3022                 
  Lines           630460      630463          +3     
  Branches         46797       46801          +4     
=====================================================
+ Hits            471825      471859         +34     
+ Misses          155247      155218         -29     
+ Partials          3388        3386          -2     
Flag Coverage Δ
Debug 74.84325% <76.47059%> (+0.00503%) ⬆️
integration 18.01569% <0.00000%> (+0.00508%) ⬆️
production 47.87897% <76.47059%> (+0.01180%) ⬆️
test 97.00150% <ø> (-0.00030%) ⬇️
unit 44.89223% <76.47059%> (+0.01077%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@JeremyKuhne JeremyKuhne added servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria 🚫 * NO-MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) servicing-approved .NET Shiproom approved the PR for merge and removed servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria labels Mar 5, 2025
@LeafShi1 LeafShi1 merged commit 02a98c7 into dotnet:release/9.0 Mar 7, 2025
8 checks passed
@LeafShi1 LeafShi1 removed the 🚫 * NO-MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 7, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
servicing-approved .NET Shiproom approved the PR for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants