Stoyo wrote on Jul 4^th, 2014 at 8:25am:


Again some Issues in diagrams i m using your latest version, please check attached diagrams.
The behavior of diagrams is not consistent, some are in proper and some not.

Stoyo wrote on Jul 4^th, 2014 at 12:54pm:


First thing its not issue of doubly links, and some links are proper and some not can u tell me exact cause behind this.
I have attached new XML is of PDF.please check.

another one thing why some arrows using orthogonal styles and some as directs?

Ok, we were missing doubled links in opposite directions. Try code below instead. We'll try to add built-in support in next few days, along with some code to pull apart the doubles, as they overlap with the current work-around.

I hope that helps,
Stoyan

// find doubles
var doubles = new Dictionary<DiagramLink, DiagramLink>();
foreach (var node in diagram.Nodes)
{
	var links = node.GetAllLinks();
	for (int i = 0; i < links.Count; i++)
	{
		var li = links[i];
		if (li.Origin == li.Destination)
		{
			li.IgnoreLayout = true;
			continue;
		}
		if (doubles.ContainsKey(li))
			continue;
		for (int j = i + 1; j < links.Count; j++)
		{
			var lj = links[j];
			if (!doubles.ContainsKey(lj) && SameNodes(li, lj))
			{
				doubles[lj] = li;
				lj.IgnoreLayout = true;
			}
		}
	}
}

OrthogonalLayout ol = new OrthogonalLayout();
ol.Padding = 20;
ol.MultipleGraphsPlacement = MultipleGraphsPlacement.MinimalArea;
ol.Arrange(diagram);

foreach (var li in diagram.Links)
{
	if (li.Origin == li.Destination)
	{
		var p = li.Origin.Bounds.Location;
		li.ControlPoints.Clear();
		li.ControlPoints.Add(new PointF(p.X, p.Y + 2));
		li.ControlPoints.Add(new PointF(p.X - 5, p.Y + 2));
		li.ControlPoints.Add(new PointF(p.X - 5, p.Y - 5));
		li.ControlPoints.Add(new PointF(p.X + 5, p.Y - 5));
		li.ControlPoints.Add(new PointF(p.X + 5, p.Y));
		li.UpdateFromPoints();
	}
}
foreach (var link in doubles.Keys)
{
	var l = doubles[link];
	link.ControlPoints.Clear();

	if (link.Origin == l.Origin)
		link.ControlPoints.AddRange(l.ControlPoints);
	else
		link.ControlPoints.AddRange(l.ControlPoints.Reverse());
	link.UpdateFromPoints();
} 

Add this method:

bool SameNodes(DiagramLink l1, DiagramLink l2)
{
    if (l1.Origin == l2.Origin && l1.Destination == l2.Destination) return true;
    if (l1.Origin == l2.Destination && l1.Destination == l2.Origin) return true;
    return false;
} 

Add (false, true) arguments to both UpdateFromPoints calls:

li.UpdateFromPoints(false, true);
...
link.UpdateFromPoints(false, true); 

These are two links placed like that by the code that handles doubles above (... link.ControlPoints.AddRange(l.ControlPoints.Reverse()) ...). If you feel the doubled links were added to the graph incorrectly by your users, you can remove all doubles from the diagram instead of copying points in the foreach in doubles.Keys loop. As I said we'll be implementing built-in support for double links in next few days and will add some code to pull them apart so they don't overlap.

var point = new PointF(0, 0);
var link = diagram.Factory.CreateDiagramLink(point, point);
link.Pen = new Pen(Color.Red, 0);
diagram.SaveToXml("test.xml"); 

creates the following XML:

<Link Class="std:DiagramLink" Id="0" Version="2">
  ...
  <Pen>
    <Color>#FFFF0000</Color>
    <DashOffset>0</DashOffset>
    <DashStyle>0</DashStyle>
    <LineJoint>0</LineJoint>
    <MiterLimit>10</MiterLimit>
    <Width>0</Width>
  </Pen> 

I hope that helps,
Stoyan