Vis Automations · In-app tool, Automation Scripts menu
Model Inspector
A Python tool that Vis lists in its own Automation Scripts menu: it attaches to the open session, reads every part, selects the largest, retitles the view, adds a snapshot and writes a report.
Verification NOT fully passing on Vis 2606.0 build 26134 + 2606.2610 · 2026-10-29 · repo tc-vis-automation 9f1b0af · The tool, the menu launch and restart persistence work; registration by registry does not.
Needs Vis 2606 installed (see Install), Python with pywin32, and a Windows .py file association. The script is inapp/model_inspector.py in the repo.
Add it to the menu (EXERCISED, once)
- Start Vis and open a model.
- Open ☰ Menu › Automation Scripts › Manage Scripts...
- Right-click the Automation Scripts root and choose New Script. Not Load: it expects a profile XML, and pointing it at a
.pygives “Error in loading script profile file”. - Script Type Python, then Browse to
model_inspector.py. - Apply, then OK. If OK raises a Save As for the profile, save it anywhere.
- ☰ Menu › Automation Scripts now lists
model_inspector.py. Click it.
Do not press Enter in that dialog. With no profile known, OK raises a Save As that can open invisibly behind another window and leave Vis disabled until the process is ended.
The entry stays after Vis restarts (corrected 2026-10-29: an earlier note here said it did not). Where Vis stores it is still unknown (see Open questions).
Run it from a shell instead (EXERCISED)
With Vis open, run the script directly. It attaches to the open session the same way the menu launch does.
python inapp/model_inspector.py
Registry registration (DERIVED, does not work)
scripts/Register-VisInspector.ps1 writes the XML profile and a FileLocation value under both HKCU\Software\Siemens\VisView\2606.0\<product>\C\VisAutomationScripts\Profile and the VisView_Retained ... Common root. With Vis restarted, the menu still lists only Manage Scripts... . Kept in the repo as the record of what was tried; do not rely on it.