Have you set the link's Style to Cascading?

Are you setting any other link properties or routing options? This works fine for me with everything else at default values:

private void diagram_LinkCreated(object sender, LinkEventArgs e)
{
	DiagramLink link = e.Link;
	link.Style = LinkStyle.Cascading;
	link.CascadeOrientation = Orientation.Horizontal;
	link.AutoRoute = true;
} 

Stoyan

Could you attach here a sample project that reproduces this, or email it to support@mindfusion.eu?

When I removed the CascadeOrientation assignment in AddProcessLink, the end point of the link could not be moved because it is covered by the middle point. Is this why you are setting the orientation to Horizontal?

It seems the problem happens because the auto-routing function does not update this flag but sets the first segment to vertical anyway when the link begins from the node's bottom center, and the link's subsequent state is not well defined. You could reset the flag to Auto once the link is connected to a node to fix this:

private void diagram_LinkModified(object sender, LinkEventArgs e)
{
	e.Link.CascadeOrientation = MindFusion.Diagramming.Orientation.Auto;
	if (!e.Link.Destination.IsDummyNode() && !e.Link.AutoRoute)
		e.Link.AutoRoute = true;
} 

Alternatively if this is only for hit-testing the last point, do not change the orientation flag but set SegmentCount to 3 - this should move the next-to-last point to the middle where it won't prevent you from dragging the end points.

I hope that helps,
Stoyan

Hi,

It seems SegmentCount value is ignored if AutoRoute is set to true. As a workaround you could set the ControlPoints collection to the desired points and then call UpdateFromPoints(true, true) to adjust the number of segments.

Also, in the latest release hit-test priority is given to the last point in the collection, so if you upgrade you'll be able to move the last point even with a straight cascading link with 2 segments (when there are overlapping points).

Regards,
Lyubo

There are no changes in the setting of link shapes in v 6.0.

Could you check, if by any chance if you're not setting ControlPoints values to these coordinates; or maybe after refactoring some style got lost when renaming link.Style to link.Shape.

If you're using anchor points and you're calling some layout algorithm, have a look at the value of the Layout.Anchoring property. Maybe the default has changed, and that could result in end points repositioning. If that's the case you could either try another Anchoring value, or set the points' locations accordingly.

Also, have a look at any event handlers that could have been disconnected - in the latest release old Event handler delegates have been removed and events are now defined as generic EventHandler types.

If you're not able to fix the problem, please attach a sample project that reproduces this behavior, so that our developer can have a look at it.

Regards,
Lyubo

I cannot see the cause of the links issue in this handler.

Check if you're modifying the ControlPoints collection after routing. That seems the most likely cause. Maybe you're setting the middle control points in a way that expects the end points to be anchored to bottom center and top center of a node.

Also, you should be aware that there is a possibility of an infinite recursion in your snippet - RouteAll will raise the LinkRouted event and the application could hang/crash if the number of links associated with a given node is greater than the number of anchor points.

Regards,
Lyubo