Hi. I am using scripting extensively these days. One can do great things with scripting. Here I spot an issue and give a suggestion for improvements:
– model.matrices returns a list of matrix views located at the root level in the model browser; matrices nested inside folders are not returned.
– Scripting manager and editor: the editor gives no feedback about coding errors, unlike the scripting console; when there is a syntax error, the action is disabled or the function set is not available. It’s tedious doing development and test in the console then copying and pasting into the editor. It would be nice having the same error message at the bottom of the editor which you have in the console. I suggest also adding a “Run action” button next to the “Hotkey” button, in order to speed up action execution during testing.
Thanks, Ben, for your informative answer. From an end user’s point of view, I cannot grasp the relevance of the “sandboxing” choice. In traditional spreadsheets, scripting allows one to do many things which are useful for automating computing tasks as well as preliminary procedures (copying and importing text files, move or copy content among open worksheets, etc. ). Quantrix scripting is more powerful and robust in many aspects, and is improving constantly. However, sometimes I feel that the constraints imposed by sandboxing are a limiting factor for the completeness and consistency of the scripting environment.
Maybe I am understating possible interferences with the correct functioning of Quantrix. Anyway, I am confident that collecting a wide range of use cases may help clarifying what would be the best match.