FAQ
Why is completion or a parameter hint missing?
Press Ctrl+J and inspect the status bar for Python or Helper errors. Parameter field completion requires direct assignment from the matching *_parameters() factory. Basic local candidates may remain when Jedi is unavailable.
Why are Check, Format, or Fix unavailable?
Check attempts Ruff and mypy; Format needs Black or Ruff Formatter; Fix uses Ruff. These failures mainly affect editing assistance and do not necessarily prevent runtime. Format-on-save falls back to saving the original text.
Why does the script fail?
Run Check, test mls.system.get_software_version(), verify paths and parameter levels, use raise_on_error=False to print error_code, message, and raw, then verify project/data/view/plug-in/license prerequisites. Open Show/Hide > Windows > Output and inspect ScriptTool records.
Why is a parameter unknown?
Top-level arguments and nested Parameters fields are validated separately and are case-sensitive where defined. Do not pass a nested field as a top-level keyword.
Why is a tool unavailable?
The ID may be wrong, the current release may not register the feature, a plug-in may be unavailable, or a license/application prerequisite may be missing. Prefer module wrappers and verify exact IDs for dynamic calls.
Why is another script reported as running?
Only one script can run. During execution you cannot run again, close the editor, switch Script Tools, or delete the running tool. There is no UI Stop command; wait for completion.
Why is print() absent from the editor Output panel?
That panel contains Check and Review findings. Open Show/Hide > Windows > Output in the main application and inspect the ScriptTool log category.
Why is result.output empty?
Not every tool creates a file. Inspect outputs, result, data, and raw.
Why is there stderr text after success?
Some Python libraries write progress or non-failure diagnostics to stderr. When overall ok=True, stderr text alone does not mean failure.
Why did external edits not synchronize?
The external application must save the temporary file. Confirm synchronization before switching tools or closing the editor, which ends the session.
Known limitations
- The
gvscripttool bridge is available only inside LiDAR360MLS. - Only one script runs at a time, with no UI Stop command.
- Normal files use UTF-8.
- Windows application selection is Windows-only.
- Idle Check is lightweight, and Review cannot cover every security or business risk.
- Tools may depend on projects, views, selections, data, plug-ins, or licenses.