There exist gaps in the online documentation for Command Scripts.
Would you kindly update the help content to include the undocumented functionality?
The single line of text in the support documents says the Command Script syntax should be like this:
'In the Key-in window, key in @<script>'
The correct syntax appears to be:
$ @"C:\path\to\my\testCommandscript.txt"
The above is particularly relevant for when the paths or filenames have name spaces. But I have found it's better to always include inverted commas as some paths don't seem to be recognised.
To use a Configuration variable in the Command Script path it must also be encapsulated within inverted commas [the $ symbol to expand variables as well]:
$ @"$(MS_SCRIPT_VARIABLE)testCommandscript.txt"
The dollar symbol $ needs to be used twice in the command line, along with the inverted commas in order to use Configuration Variables properly in the Command Script command line. Not documented.
Additionally, the hash # symbol can be used in the Command Script to add by-line comments that are not executed by the CAD Input Queue. This is not documented. I found this by accident after copying/renaming a Config File, and I then found it on a blogger's page. Nowhere on a Bentley support page.
In addition to this, Action Strings can also be used in Command Scripts:
E, T, M, and even waiting for user input with %d
Command Strings can also be chained in the Command Script using the semicolon:
place circle center; xy=1,2,3; dx=4,0,0
Inverted commas can also be used to frame strings if they have spaces in between.
M,cf"Write a message here AT THE LEFT PROMPT"
These additional syntax options should also be included and explained in the support documents.
If they are clearer and fairer then I think more entry level users might start using Command Scripts via Function Keys or Custom Buttons.