Skip to content

Conversation

@SatishRaj4377
Copy link
Contributor

Description

  • Highlighted the property
  • Added question marks to the "See Also" links

@SatishRaj4377 SatishRaj4377 self-assigned this Jun 14, 2024
@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: WPF-889895-SnapConstraints_Page_Issues

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: WPF-889895-SnapConstraints_Page_Issues
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
FT Layout Syntax Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0

@SatishRaj4377 SatishRaj4377 changed the base branch from master to development June 14, 2024 09:05
@SatishRaj4377 SatishRaj4377 changed the base branch from development to hotfix/hotfix-v26.1.35 June 18, 2024 05:27
This feature allows the diagram objects to snap to the nearest interaction of gridlines while being dragged or resized. This feature enables easier alignment during layout or design.

Snapping to gridlines can be enabled or disabled with the [SnapConstraints](https://help.syncfusion.com/cr/wpf/Syncfusion.UI.Xaml.Diagram.SnapConstraints.html) property of SnapSettings. Default value is None.
Snapping to gridlines can be enabled or disabled with the [`SnapConstraints`](https://help.syncfusion.com/cr/wpf/Syncfusion.UI.Xaml.Diagram.SnapConstraints.html) property of SnapSettings. Default value is None.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need of highlight for the linked property. Please highlight the SnapSettings class in the file.

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: WPF-889895-SnapConstraints_Page_Issues

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: WPF-889895-SnapConstraints_Page_Issues
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
FT Layout Syntax Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0


## How to change the snap indication style

When snapping, cyan shade color indication lines will be shown. These indication lines styles can be customized by using the [`SnapIndicatorStyle`](https://help.syncfusion.com/cr/wpf/Syncfusion.UI.Xaml.Diagram.SnapSettings.html#Syncfusion_UI_Xaml_Diagram_SnapSettings_SnapIndicatorStyle) property of SnapSettings class.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the highlight for the SnapIndicatorStyle property.

…he properties with link as Suggested in the Review
@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: WPF-889895-SnapConstraints_Page_Issues

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: WPF-889895-SnapConstraints_Page_Issues
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
FT Layout Syntax Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0

Copy link
Collaborator

@KarkuvelRajan KarkuvelRajan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@KarkuvelRajan KarkuvelRajan merged commit 8ccb4b6 into hotfix/hotfix-v26.1.35 Jun 26, 2024
@KarkuvelRajan KarkuvelRajan deleted the WPF-889895-SnapConstraints_Page_Issues branch June 26, 2024 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants