EA 11: EA_OnPreNewElement ParentID always 0

[McMannus]

Hi guys,

I'm about to migrate our add-ins to EA11. I'm using EA 11.1106.

Problem: When dragging an element from the toolbox into another element in a diagram, it used to be the case with EA10 that the parameter  with the event properties stored the parent id of the element in the second index.
However, with EA11, this parent id is always 0.

I tried this with UML classes and components and it didn't work.

In addition, I noticed that the dashed line in the element where you drag the other one into, doesn't appear during the dragging process. This was also different in the old version.

Any advice?

[qwerty]

I guess this is quite exotic so rather unlikely someone else has encountered it. If nobody answers within the next 2 or 3 days you should send a bug report.

q.

[Jonathan Lubach]

Hi McMannus,

I also encountered this in EA 11. I must admit, that I never tried this one in older version but for me it would also be helpful If the ID of the parent object is filled correctly.

Did you send a bug report to SPARX?

Jonathan

[McMannus]

Hi Jan,
 
Regarding the issue you mentioned below.
 
Our developers have confirmed that this is a bug and it is logged to be fixed. We cannot yet say when (in which build) the fix will be implemented.
 
If you have further questions or issues please let us know.
Best Regards,

Simon Cotching
Sparx Systems Pty Ltd


ISSUE DETAILS

Subject:
EA_OnPreNewElement parameter incorrect

Details:
I have created a profile with a stereotype called Inport extending the metaclass Port.
In addition, I have created a UML component (not the package component) and put it as a link in a Logical Diagram.
When I drag the Inport from the toolbox to the component in the diagram, the parent id in the event properties of the EA_OnPreNewElement is always equal to 0, although it should be the Object ID of the component.
I noticed that the correct parent ID is set if I drag the standard port from the Component Toolbox.
In addition, the behavior is also wrong for custom stereotypes extending the metaclass Part, so I think this is a general problem with stereotyped elements.