Hello Stoyan !

I have a new issue for you hahahah.

In out project we are using the SubordinateGroup of the ShapeNode (not containers) for any custom needs we have.

I am not sure it's a good idea anymore. It seems that when we add the ShapeNode to any container it change its SubordinateGroup . its SubordinateGroup.AttachedNodes are resetted so it break everything.

Is there a way to prevent this from being changed when we add the node to a container or do we have to change our code and not use this anymore ?

Thanks

Hey,

no not at all.
I just use the container.add(node) function.

and when I debug the code I can cleary see that this call kills the SubordinateGroup.

to modify the group of the node we use :
node.SubordinateGroup.AttachToCorner(container, 0);

Can it be a bug related to the old version I have ?

Good Morning Stoyan !

We are using v5.3 Beta...

Here is with more precision what we do :

We use CustomShapeNode associated with CustomContainerNode...
Each CustomShapeNode is displayed with its CustomContainerNode underneath which is important for our project. 

When we create the CustomContainerNode to be associated with the CustomShapeNode we call :

AssociatedCustomShapeNode .SubordinateGroup.AttachToCorner(this, 0);
 

This way we can access the CustomContainerNode  from the CustomShapeNode  via :

CustomShapeNode  .SubordinateGroup.AttachedNodes[i] as CustomContainerNode
 

And this works perfectly.

But since recently we decided to add container in our project to add functionalities to our diagrams...
ShapeNode and its associated CustomContainerNode into our containers.

But when we add the CustomContainerNode associated to the ShapeNode already in the container by calling

container.Add(CustomContainerNode);
 

this modify the CustomShapeNode.SubordinateGroup of the CustomShapeNode associated to the CustomContainerNode just added...

It`s 100% repro...

I hope it's clear :S

Thanks again Stoyan

YES !

that works perfectly you are right !
Thank you so much for the help one more time !!!!