So, should these GSMs have the subtype "Macro" or "Drawing Symbol" ?
I don't think it really matters.
As far as I know the subtype only adds a particular set of non-editable (as in the parameter name) parameters automatically to the object.
So you choose the sub-type that gives you the best option of pre-set parameters that you want.
One of the forum moderators. Versions 6.5 to 25 Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10 Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10
The subtype... is the fastest way to have the common parameters propagated through the library... and basically that's all apart from the functionality (in some situations)... the common object can be a macro to any subtype though.
PS. Sidenote: If You want to spread some parameters between objects and not wiling to use xml due to own preferences and not wiling to use subtypes: just make a copy of the part that has all of needed parameters...make it a subtype. Use it as a template to the other objects... then delete the subtype element.
My question is more in the direction that if case I have a un-"placeable" macro, that admits different subtypes, should it still be a "Macro" or another subtype that is applicable (from a the point of view of office standard) ?
I think that I will go with this:
1. If not placeable, then Macro
2. If placeble then what ever applies
A good friend of mine have once told me that I´m so brute that I´m capable of creating a GDL script capable of creating GDLs.