DiagramObject.ElemenID Assignment

[Neocortex]

I'm trying to direct the DiagramObjects in a particular diagram to a different Element in the model. I make the Assignment and call update ... no exceptions are thrown, but the newly assigned ElementID is not persisted.

We have made sure that all DiagramLinks also refer to the newly assigned ElementID if necessary ... and they are persisted with no problem.

[Geert Bellekens]

Hi,

I've encountered the same problem and reported the bug to Sparx.
My solution was:
(this code is an operation on my DiagramNode wrapper that wrapps the actual EA.DiagramNode)

Code: [Select]

/// <summary>
        /// set the element this node represents
        /// </summary>
        /// <param name="element">the element this node represents</param>
        public void setElement(UMLElement element)
        {
            // there seems to be a bug in the com object when calling update on the DiagramObject after setting the elementID
            // workaround could be to create a new diagramObject on the diagram and copy all the settings
            EA.Diagram parentDiagram = model.getWrappedModel().GetDiagramByID(this.wrappedDiagramNode.DiagramID);
            //get the index of this diagramnode in the collection of diagramobjects of the parent
            short index = -1;
            for (short i = 0; i < parentDiagram.DiagramObjects.Count; i++)
            {
                if (((EA.DiagramObject)parentDiagram.DiagramObjects.GetAt(i)).InstanceID == this.wrappedDiagramNode.InstanceID)
                {
                    //found the correct one.
                    index = i;
                }
            }
            //create a new diagramobject
            EA.DiagramObject newDiagramObject = (EA.DiagramObject)parentDiagram.DiagramObjects.AddNew("", "DiagramObject");
            //set the new elementid
            newDiagramObject.ElementID = element.getID();
            //copy position attributes
            newDiagramObject.bottom = this.wrappedDiagramNode.bottom;
            newDiagramObject.left = this.wrappedDiagramNode.left;
            newDiagramObject.right = this.wrappedDiagramNode.right;
            newDiagramObject.top = this.wrappedDiagramNode.top;
            //delete the old diagram object
            parentDiagram.DiagramObjects.Delete(index);
            //reference the new diagram object
            this.wrappedDiagramNode = newDiagramObject;
            // bug reported to Sparx support. If they fix it this original code can be used again.
            //original code: this.wrappedDiagramNode.ElementID = element.getID();
            
        }It ugly, wrong  and waaay too much code, but it works  

Geert

[Neocortex]

Thanks heaps Geert !!

[MagnusH]

This forum is great!

But the bug is really bad for me. All diagramlinks are of course destroyed when the original diagramobject is deleted and have to be rebuilt also. Any trick to do that in a good way without destroying custom line layout?

Thanks,
Magnus

[Geert Bellekens]

Magnus,

I don't see why the diagramlinks would be destroyed.
As far as I can see they relate to a connection, which isn't changed in any way.
As long as you make sure the connector points to the correct objects there shouldn't be a problem.

Geert

[MagnusH]

Geert,

You're right. They were preserved as long as a a change the client/supplier on the connection before deleteing the diagramobject.

// magnus