Author Topic: Strict Connector Syntax results in wrong connector  (Read 2378 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Strict Connector Syntax results in wrong connector
« on: April 01, 2020, 01:04:41 am »
Hi all,


Upon the advice received in this thread, we've begun the process of upgrading to 15.1.1527.

In 1527, the management of the Strict Connector Syntax and/or Quick Linker is, in a word, f*cked.

It doesn't work, and what's more, it's not consistent.


I have some custom MDG Technologies. Following the instructions in the documentation, I can't get the Quick Linker to trigger correctly for (non-stereotyped) Send and Receive elements in a custom Activity diagram. That's what the other post is about.

Now in 1527, my MDG Technologies do contain Quick Linker definitions, but not ones that affect Send, Receive or anything else in my custom Activity diagram. I've deleted those.

My custom toolbox includes ControlFlow, but not ObjectFlow.

With Strict Connector Syntax enabled, in my custom Activity diagram, EA creates an ObjectFlow when told to create a ControlFlow. If the requested ControlFlow is between two Actions, ActionPins are created as well. If the requested ControlFlow is between a Send and an Action, no ActionPin is created (but the connector is still an ObjectFlow).

If I use the Quick Linker to draw a connector from a Send to a Receive,  with "Filter to Toolbox" enabled, the Quick Linker menu does not include ControlFlow. Which is in the toolbox.
With "Filter to Toolbox" disabled, ControlFlow still doesn't appear -- but ObjectFlow does.

This behaviour sometimes hangs over into vanilla Activity diagrams as well, sometimes not.

Broken.
Doesn't work.
Clearly not even tested.

What do I do to fix it?


/Uffe
My theories are always correct, just apply them to the right reality.