ID 378316 - Executing certain tool commands in a recorded macro that has been stored in a configuration file fails to execute

Problem summary
Executing certain tool commands in a recorded macro that has been stored in a configuration file fails to execute in the Command History window. An error message appears explaining that the "Command Block" is validated as an unknown command in the macro.

The issue seems to appear for only some tool commands, for example the Bevel tool, that are recorded to the macro, where the "Command Block" encapsulates any tool attributes that have been set for these certain tools while recording to the macro. 

Customer reported version
Modo 12.2v1 

Customer reported platform
MacOSX 10.14 

Steps to reproduce

1) Open Modo.

2) Create a cube and select some edges to use with the Bevel tool. 

3) Click on the red circle that is shown in the right bottom corner of the window. Select the "Record Macro" icon to start recording tool commands with the Macro Recorder. 

​

4) Activate the Edge Bevel tool and bevel the cube by changing the tool handles in the viewport. 

5) Drop the tool and then click on the "Stop Record" icon to stop the Macro Recorder. 

6) Open the Macro Options and then select the option "Store in Config". Give the macro a name and then click "OK" to store the macro in the configuration file. 

7) Press "F5" to open the Command History. Change to the "Scripts" tab and expand "Macros (Config)" to find the stored macro in the expanded list.  

8) Double-click on the macro and now there is an error message appearing explaining that the "#Command" block is validated as unknown.

9) Go to the Luxology folder and open the configuration file in a text editor. 

10) Search for the name of the stored macro and the execution is stopped at the line where the Command Block encapsulates certain tool adjustments that have been previously recorded to the macro. In versions earlier than 11.2v1, these Command Blocks are not added for the tool adjustments and the macros are executed correctly.

​

Workaround

1) Create a cube and select some edges to bevel. 

2) Start recording the macro and then activate the bevel tool. 

3) Change attributes of the Bevel tool and then stop recording the macro.

4) In the Macro Options, select "Save to file" and store the macro in an LXM file. 

5) Select some other edges of the cube to bevel with the saved macro. 

6) Start recording a second macro. 

7) Go to System -> Run Script and then select the saved LXM file. Notice that the macro is now working running it from the LXM file. 

8) Stop recording the second macro. Open the "Macro Options" and then select to store the new macro in the configuration file. 

9) Press "F5" to open the Command History window. Change to the "Scripts" tab and then expand the "Macros (Config)" list to find the new macro. 

10) Select edges of the cube and double-click the macro from the list. The macro is now executed correctly. 

Reproduced by support

This bug has been reproduced in:
Modo 12.2v1 - Windows 10 - CentOS 7 - MacOSX 10.13 
Modo 12.1v2 - Windows 10
Modo 12.0v1 - Windows 10 
Modo 11.2v3 - Windows 10 
Modo 11.2v2 - Windows 10 
Modo 11.2v1 - Windows 10 - CentOS 7 - MacOSX 10.13 - regression

Earliest version tested
11.1v1 - This issue no longer appears in this version and has regressed

Expected behaviour
All recorded tool commands in a macro should be executable in the Command History window when the macro is stored in the configuration file. 

Actual behaviour
Executing a recorded macro that has been stored in the configuration file fails to execute because of the Command Block in the macro that is validated as an unknown command.