EClass EdgeDefinition
The equivalent of DropReception for EdgeRouting. An EdgeDefinition is selected if both anchors.selectionQuery are met. Then the .routingCommand is run.
- ePackage:
- contained by:
EAttributes
- documentation (EString)
Deprecated since version 0.3.0.
@deprecated
- isStrict (EBoolean)
Click SOURCE first, then TARGET. If false, order is ignored.
Defines whether the tool handles edge directionality strictly. This setting affects only uni-directional edges. In strict mode, for uni-directional edges the source must be selected by the user first and the edge must be dragged towards the target. In non-strict mode the order of source/target is ignored and it is only checked whether a valid edge definition can be generated from the selection. The non-strict mode is for unambigous cases only. Use with caution.
- name (EString)
Defines the EdgeDefinition’s name. Since an EdgeRouting can have multiple edgeDefinitions, the name is great to differentiate them.
- prepareTemplate (EBoolean)
Deprecated since version 0.3.0.
@deprecated
- templateAlias (EString)
Deprecated since version 0.3.0.
@deprecated
EReferences
- anchors (Anchor) (lowerBound=0, upperBound=-1) (containment)
Define the possible SOURCE and TARGET for the EdgeDefinition. Based on this, the EdgeDefinition is selected. Can be only one anchor, e.g. “any Gate” “@CLASS@ALLSUPERTYPES/name&ANYGateA” Trivial case: two anchors, SOURCE and TARGET, e.g. @CLASS=(@(CLASS,’http://www.oaam.de/oaam/model/v160/functions’,Input)) You can also have multiple anchors to either allow a lot or specify SOURCE and TARGET precisely. E.g. Hardware.editorModel EdgeRouting Connections
- routingCmd (CompoundCmd) (lowerBound=1, upperBound=1) (containment)
The EOQ commands run when EdgeDefinition is chosen based on the anchors. Use the alias SOURCE, TARGET and EDGEITEM (if using TEMPLATE)
E.g. SET #{EDGEITEM} source #{SOURCE}; ADD #{EDGEITEM} ‘targets’ #{TARGET}; ADD #{ROOT} signals #{EDGEITEM}
(Not that for legacy reasons, here ROOT means EDITORROOT.)