Parent/Child Relationships in Diagrams

[fwoolz]

Hello All,

This is an extension of an earlier post on the Automation Interface forum...

EA 6.1 and 6.5 beta 1 do not appear to handle parent-child relationships between elements and regions in Activity diarams consistently. In some cases, elements placed within a region appear below the region in the Project Browser as children (and a check of the database agrees); in other cases the elements do not show up as region children but can be dragged under the region; and in still other cases (e.g. Merge nodes, Decisions, and ExpansionRegions) EA refuses to allow the elements to be dragged under region elements as children. The database can be hacked and the ParentID field can be modified directly; EA doesn't appear to have a problem with this since the element hierarchy changes accordingly once the project is reloaded.

I'm speculating that this is a legacy feature dating back to the days before everything in UML, just about, became viewed as a "classifier".

Cheers,

[«Midnight»]

There is a known bug in 6.5 beta 1 regarding merge nodes. It will apparently be resolved in beta 2. You should characterize your observations as well as quickly possible and issue a bug report (via the EA main menu - Help / On-line Resources / Bug Report Page).

My thinking is that you might catch Sparx when they are working in this same area of the product. That could result in a better product in a shorter time frame. It might also help them move the engine away from legacy baggage.