Named Mate Connectors

lemon1324

When manually creating a mate connector, renaming the mate connector feature (e.g. to "First") will result in that name appearing in the mate query box in an assembly (e.g. "First of Part").

Is it possible to achieve the same functionality for mate connectors placed using a FeatureScript that places many mate connectors at once? Neither mateConnector() nor opMateConnector() appear to take a name parameter. Is it possible to set an attribute, or is this functionality in Assemblies implemented outside the scope of what FeatureScript can access?

Alex_Kempen

If manually renaming a mate connector causes the assembly to update, then renaming mate connectors using setPropery with PropertyType.NAME and value equal to your name should do the trick. Be warned, however, that creating multiple mate connectors per feature can be pretty reliable from a robustness perspective; setExternalDisambiguation (and, by extension, forEachEntity) don't work for mate connectors which have been used in an assembly, resulting in behavior like reordering or removing queries breaking all uses of mate connectors in assemblies for that feature.

kevin_o_toole_1

Unfortunately mate connectors are currently named in assemblies via their *feature* name, which is not something which exists or is settable in FeatureScript for mate connectors created inside non-mate-connector features.

You can file an improvement request to add this capability!

Jonathan_Hutchinson

I don't quite get this - is there a workaround to be able to name the opMateConnector result from a sting input parameter?