Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[release/9.0] fix #13305 Baseline SnapLines do not appear in DesignSurface #13349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 8, 2025

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 23, 2025

Backport of #13324 to release/9.0

The cause of this issue

This issue is caused by PR10279

These are two of all changes make in PR10279
image

BehaviorService, DragAssistanceManager use SnapLines to add some effects during design time.

ControlDesigner has a virtual property SnapLines, but most designers override the property, in other words, most designers have customized SnapLines

Code flow before PR10279

when BehaviorService or DragAssistanceManager accesses SnapLines , customized SnapLines were returned.

Code flow after PR10279

ControlDesigner.cs

image

when BehaviorService or DragAssistanceManager accesses SnapLinesInternal , customized SnapLines were skipped.

Proposed changes

  • Use SnapLines

Screenshots

Before

Image

After

Image

Test methodology

  • manually

@github-actions github-actions bot requested a review from a team as a code owner April 23, 2025 01:50
@Epica3055 Epica3055 closed this Apr 23, 2025
@Epica3055 Epica3055 reopened this Apr 23, 2025
Copy link

codecov bot commented Apr 23, 2025

Codecov Report

Attention: Patch coverage is 97.72727% with 1 line in your changes missing coverage. Please review.

Project coverage is 74.86194%. Comparing base (61ec31a) to head (4e0694c).
Report is 16 commits behind head on release/9.0.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           release/9.0      #13349         +/-   ##
=====================================================
+ Coverage     74.83837%   74.86194%   +0.02357%     
=====================================================
  Files             3022        3022                 
  Lines           630464      630506         +42     
  Branches         46801       46801                 
=====================================================
+ Hits            471829      472009        +180     
+ Misses          155246      155114        -132     
+ Partials          3389        3383          -6     
Flag Coverage Δ
Debug 74.86194% <97.72727%> (+0.02357%) ⬆️
integration 18.02409% <50.00000%> (+0.01304%) ⬆️
production 47.91853% <50.00000%> (+0.04851%) ⬆️
test 97.00042% <100.00000%> (+0.00037%) ⬆️
unit 44.95149% <0.00000%> (+0.06962%) ⬆️

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.

@Epica3055 Epica3055 self-assigned this Apr 24, 2025
@Tanya-Solyanik Tanya-Solyanik 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 Apr 24, 2025
@Tanya-Solyanik Tanya-Solyanik added this to the 9.0.6 milestone Apr 24, 2025
@Tanya-Solyanik Tanya-Solyanik merged commit f8fd991 into release/9.0 May 8, 2025
8 checks passed
@Tanya-Solyanik Tanya-Solyanik deleted the backport/pr-13324-to-release/9.0 branch May 8, 2025 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚫 * NO-MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) servicing-approved .NET Shiproom approved the PR for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants