MDG Technologies with and without old quick linker definitions

[Uffe]

I have two MDG Technologies, A and B. There are some dependencies -- RefGUID stereotypes, that sort of thing -- from A to B but none the other way around.

I have been working to replace the recently obsolescent quick linker definitions from A with metamodel constraints. B never had any quick linker definitions, but in B I have added _HideUmlLinks True attributes to all the metaclasses.

When I use a recent version of A, with metamodel constraints and no quick linker definitions, I get the behaviour I want that the metamodel constraints let me specify. But if I instead use an old version of A, with quicklinker definitions instead, the behavior of stereotypes from B changes.

In a custom diagram out of A I have two elements with stereotypes from B.
With the metamodel constraint version of A, the quick linker doesn't let me draw any connectors between the two elements. As expected.
With the quick linker definition version of A, the quick linker suddenly shows a bunch of different possible connectors between the two elements.

Remember: the B version never changes. The elements don't change (I don't delete and recreate them). All that differs between sessions is the version of A.

So when one MDG Technology is built with quick linker definitions, it breaks the _HideUmlLinks behaviour in a different MDG Technology.