Red border occurs on mouseover on custom node while connecting two custom node

[ashish]

Hi,

I have custom nodes implemented in my application. But when i try to connect those two nodes by line connector then red border appears while connecting and when node is connected it disappear.

How to restrict that red border from appearing while connecting custom nodes.

Sample image has been attached

Attachment: RedBorderNode_9b6ee531.zip

[Ranjitha Amirthalingam]

Hi Ashish,

Thanks for contacting Syncfusion support.

Requirement: Disable/Customize the Connection Hit Path Border of Node and ConnectionPort.

We have achieved your requirement by HitPathStyle property of Node and ConnectionPort. We have provided code example and sample to represent this. Please refer to the sample and code example as below.

Code example:

Xaml:

<Style x:Key="Hitpathstyle" TargetType="Border">

     <Setter Property="BorderBrush" Value="Transparent"></Setter>

     <Setter Property="BorderThickness" Value="4"></Setter>
</Style>

C#:
node.HitPathStyle=this.Resources["Hitpathstyle"] as Style;

port.HitPathStyle = this.Resources["Hitpathstyle"] as Style;

//Here, node is the instance of Node and port is the instance of ConnectionPort.

Sample Link:  ConnectionHitBorder


Also, we have provided video to represent this. Please refer to the video as below.

Video Link: ConnectionHitborder_video


Regards,
Ranjitha A.

[ashish]

Hi Ranjitha,

Thanks for the quick reply.

When we downloaded the sample application provided by you we are getting error for

node.HitPathStyle

Kindly find the error message attachment.

We are using 13.3460.0.7 version of syncfusion

Thanks,
Ashish Nandavadekar

Attachment: Error_52644b0b.zip

[Ranjitha Amirthalingam]

Hi Ashish,

Requirement: Need to disable/customize the Connection Hit Path Border of Node and ConnectionPort.

We have provided support to disable/customize the Connection Hit Path Border using HitPathStyle property in our Volume 4 release( 13.4.0.53 version. These properties will work in 13.4.0.53 version. Please upgrade to our latest version(13.4.0.53) to get your issue resolved.




Regards,
Ranjitha A.