Just noticed few cases in diagramView that:

{no problem case}
1) on init (first load or a postback) when you sample and create 2 nodes and after that you create link between them. Link is created and works perfect.

{problem case}
2) on callback, you have diagram object in session. You load the object and find target (A & B) nodes and you create link between them. The link is not created (failed to create one). The link object contains all necessary details and information that is set to it but when you debug the diagrams data and look for links (linkCollection) there is link count 0 [zero].... I have put a try-catch to get hold of possible problems, but result is without any errors... I find this as a bug... (or I'm missing something really important here...)

Any help would be great...

Br. Henry

Like this:

private bool _createLinkNode(string linkText, Color linkTextColor, string nodeTag, DiagramNode org, DiagramNode dest){
....
DiagramLink link = diagram.Factory.CreateDiagramLink(org, dest);
...
}
 

But I just resolved it... don't know why, but this works:

private bool _createLinkNode(string linkText, Color linkTextColor, string nodeTag, DiagramNode org, DiagramNode dest){
....
DiagramLink link = diagram.Factory.CreateDiagramLink(diagram.GetNodeAt(org.Bounds.Location), diagram.GetNodeAt(dest.Bounds.Location));
....
}
 

But now I have sequel problem related to this.
Now on diagram arrange all nodes vanishes (only in case when a link is created || one or more)....
Also noticed that Diagram Bounds are messed because of this... default: (0,0, 2000, 1500)... after link creation + diagram_arrange (-23.3, -46.5, 2158, 1532). (note: this number is random, but mainly X & Y goes minus)....

DiagramItemCollection childNodes = null;
LayeredLayout ll = null;

/* FROM HERE */
/* ** will arrange nodes in containers ** */
// get nodes collection in diagram
foreach (DiagramItem di in diagram.Nodes){
	Type t = di.GetType();

	// find node type "ContainerNode"
	if (t.Name.ToUpper() == "CONTAINERNODE"){
		// get all nodes in container nodes and set them to a node collection to be arranged.
		ContainerNode cn = di as ContainerNode;
		if (cn.SubordinateGroup != null){
			childNodes = new DiagramItemCollection();

			foreach (DiagramNode childNode in cn.SubordinateGroup.AttachedNodes){
				childNodes.Add(childNode);

				foreach (DiagramLink link in childNode.OutgoingLinks)
					childNodes.Add(link);
			}

			ll = new LayeredLayout();
			ll.LayerDistance = 50;
			ll.NodeDistance = 60;
			ll.Orientation = MindFusion.Diagramming.Layout.Orientation.Horizontal;

			ll.Arrange(diagram, childNodes);
			cn.UpdateBounds(true);
		}
	}
}
/* TO HERE */

ll = new LayeredLayout();
ll.LayerDistance = 50;
ll.NodeDistance = 100;
ll.SplitLayers = true;
ll.Orientation = MindFusion.Diagramming.Layout.Orientation.Horizontal;

ll.Arrange(diagram);

// ======================

public Diagram diagram
{
    get { return Session["diagram"] as Diagram; }
    set { Session["diagram"] = value; }
}
 

Diagram.Factory.CreateDiagramLink might fail if the specified origin and destination nodes are not in that same diagram. I imagine this would cause the problem:

org = diagram.FindNode(...);
dest = diagram.FindNode(...);
diagram.LoadFromString(...);
// org and dest are no longer references to objects in diagram
_createLinkNode(org, dest);

I can reproduce containers expanding when AutoShrink is set to false - then UpdateBounds only grows a container to include the new positions of its child nodes (that were set by LayeredLayout), but will not reclaim any unoccupied space. If you set AutoShrink to true, containers shouldn't expand any longer.

I hope that helps,
Stoyan