Quote:


Domain properties shouldn't be related to position of crossing decorations. Please only register the classes (without overriding serialization methods) and attach the xml file, so we can trace this with your node and link coordinates.

Regards,
Slavcho
Mindfusion

We do not need to see values of you custom properties for derived node types, but only node and link coordinates from SaveToXml result. It should be enough to register the custom DiagramItem type, without overriding its serialization methods to handle the added properties. Custom types might matter if you assign their instances to Tag or Id properties. In such case try handling SerializeTag event and just set args.Handled = true.

Alternatively, export coordinates in some simple format as below. Restoring the diagram from that should still show your link crossing positions for our developer to inspect:

var writer = new StreamWriter("diagram.txt");
writer.WriteLine(diagram.Nodes.Count);
foreach (var node in diagram.Nodes)
{
	writer.WriteLine(node.Bounds);
}
writer.WriteLine(diagram.Links.Count);
foreach (var link in diagram.Links)
{
	var orgIndex = diagram.Nodes.IndexOf(link.Origin);
	var dstIndex = diagram.Nodes.IndexOf(link.Destination);
	writer.Write("{0} {1} {2} {3} ",
		orgIndex, dstIndex, (int)link.Shape, link.ControlPoints.Count);
	foreach (var point in link.ControlPoints)
	{
		writer.Write(point);
		writer.Write(" ");
	}
	writer.WriteLine();
}
writer.Close(); 

Regards,
Slavcho
Mindfusion

It should try using Serializable only if those classes are used as (part of) Tag or Id values, and you can skip them by handling SerializeTag event.

The problem with missed decoration was that points are not collinear, with small difference in Y coordinates. This build give them a couple of pixels leeway -

https://mindfusion.eu/_beta/wpfdiag393.zip

Regards,
Slavcho
Mindfusion