I have turned off @CMDECHO before calling the command() function, but there are still messages generated during the command execution. Why?
Turning off @CMDECHO does not necessarily mean that the system will not echo any input nor issue any message to the command area. There are certain conditions which must be checked: 1. The script must be active and effective at the time a message is to be suppressed. This means that the next input must be taken from the script and should not be a ‘/’ code to switch the system to the man/machine interface. 2. Certain error messages and reports of command result can not be suppressed (especially when the report generation itself is the purpose of the command). All messages other than the above conditions should be suppressed by the specification of @CMDECHO. If there is any message violating the rules, please report us the command name that causes the problem. However, most of the offending cases are found to violate the first rule mentioned above. For example, the expression command(“SELECT c p1 p2 ^M”); is issued to select objects by window crossing with two given points. As the last ‘
