How to make own quick linkers defined in custom CSV & MDG replace Archimate QLs?

[adepreter]

Today , in a custom MDG including a Quick Linkers CSV, I redefined all built-in ArchiMate elements and connectors by
using the technique so called "Create Stereotypes Extending non-UML Objects" (https://sparxsystems.com/enterprise_architect_user_guide/15.1/modeling/non-uml_metatypes.html).

But when I do that my restricted Quick Linkers CSV is ignored and I get all possible default quick linkers instead based on the connectors available in the toolbox.

Does anybody knows how to disable this default EA behavior that shows plenty of ArchiMate quick linkers notably based on the connectors available in the toolbox?
(I don't want the quick linkers to be constrained by the toolbox)

[Geert Bellekens]

You are probably better off to use the meta-constraints, the QL CSV is deprecated now.

There is a property you can set (_HideUMLLinks?) to make sure you don't allow any of the base type links.
Then you have to create your own allowed links as meta-constraints.

Geert

[Uffe]

There is a property you can set (_HideUMLLinks?) to make sure you don't allow any of the base type links.

Yes, _HideUmlLinks with initial value true in the metaclass.

Not available in the profile helper, you must create it manually (in 15.0 anyway).

/U

[adepreter]

Thank you Geert and UFE.
Yes I tried the _HideUMLLinks. But it does no work for hiding ArchiMate links.

So what's the point of having a stereotype specialization capability ...
Well, I will then keep my set of ArchiMate elements and connectors with all icons and shape scripts so I don't have to drag the built-in ArchiMate metamodel with it... which I don't (re)define using a metamodeling language as it quickly becomes unreadable.

For the work I am doing at least, I find (generated) QL CSVs much simpler and more convenient than (generated) meta-constraints.

Cheers,
Alain