Fix fabricated shortcuts and behaviors across four pages
Audited every English wiki page against source this session. Pages
already citing specific source files (variables.md, autonumbering.md,
element_editor.md, preferences.md, collection_browser.md and others
fixed earlier) held up under spot-checking. The four pages here had
none of that discipline applied and each repeated the same class of
fabricated claim, now checked and corrected:
- **Rotate is Space, not R.** R isn't bound to anything in the diagram
editor -- checked ShortcutManager's registry directly.
- **Zoom in/out is the platform's standard zoom key, not bare +/-.**
QKeySequence::ZoomIn/ZoomOut, not a literal + or - keypress.
- **Double-click on an element or wire opens its Properties dialog,
not an inline text box.** Checked directly:
QetGraphicsItem::mouseDoubleClickEvent() and
Conductor::mouseDoubleClickEvent() both call editProperty(). Type
Document JavaScript scripting (--run, Run Script...)
New page: scripting.md -- the two entry points, every qet.* method
(read the model, export/save, edit geometry with real undo, navigate/
message), three worked examples, exit codes, and the same limitations
the source's own class doc comment states, kept in sync deliberately.
Updates api_reference.md and cli_reference.md, both of which currently
say plainly that QET has no embedded scripting language -- true until
now. api_reference.md in particular carries a September 2026 correction
notice from when this page wrongly claimed Python scripting and a
plugin system existed; updated to state precisely what changed (a real
JavaScript engine) and what still has not (no plugin system, nothing
runs automatically, no project file can carry or trigger a script).
Status: describes PR #891, not yet merged into master. Every new/
changed section says so. Pushing now for discoverability rather than
waiting for merge, per explicit direction; drop the pending-PR notices
once #891 lands.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Correct the automation docs: QET has no Python scripting and no plugins
api_reference stated "QElectroTech supports Python scripting" and
"QElectroTech supports plugins for deep integration", and told readers to
install plugins into ~/.local/share/QElectroTech/plugins/ and platform
equivalents. None of it exists: there is no QPluginLoader anywhere in
sources/, no plugin ABI, and every Python reference in the tree is the
launcher for qet_tb_generator -- a separate PyPI program QET starts as an
ordinary child process. QET never reads those plugin paths.
cli_reference had the mirror-image error, calling the shipped headless
export "Future CLI Features (QET 2.0)" and sending readers to the
scripting that does not exist. The FR/DE CLI pages additionally invented
a --dpi option and QET_PLUGIN_PATH / QET_ELEMENT_PATH, and documented an
argument order the parser cannot accept.
Rewrites api_reference (EN/FR/DE) around what is actually there: the 13
CLI verbs with their real positional syntax and exit codes, the real .qet
and .elmt XML (the old skeletons were invented -- no <diagrams> wrapper,
element has no id, uuid is an attribute), qet_tb_generator, and the C++
source. Adds a section naming what does not exist, so the claim does not
come back.
Also corrects the same claims where they had spread: features, history,
faq, user_manual (EN/FR/DE) and the sidebar.
ispyisail