Hi,

ContainerNodes just group other elements of same parent diagram, so whatever you add to a container must be added to the diagram indeed.

Quote:


There'll be some difference if you fold the container - attached nodes won't hide but added one will do. We plan to re-implement containers without using groups soon, so Add won't use AttachTo then anyway.

Quote:


From our side it's much easier if the diagram has direct access to all nodes including children in containers, especially in situations such as links connecting nodes from different containers, moving child nodes between containers, etc. Maybe you could implement true nesting by showing a child Diagram inside DiagramNodeAdapter inside the parent Diagram, as long as you don't need to draw links between nodes of child diagrams, and doing some re-parenting of child nodes when moving between containers.

Quote:


There's the TransformDiagramToItem method you could use to transform a child node's position to container-relative one:

void OnContainerChildAdded(object sender, ContainerChildEventArgs e)
{
	var diagramPos = e.Node.Bounds.Location;
	var localPos = e.Container.TransformDiagramToItem(diagramPos);
	Debug.WriteLine("diagram: " + diagramPos);
	Debug.WriteLine("local: " + localPos);
} 

Regards,
Slavcho
Mindfusion