From 64c180d84b44acc7bc5d8a367ed2a41682acb03d Mon Sep 17 00:00:00 2001 From: Samer Ayadi Date: Mon, 3 Aug 2026 15:56:16 +0200 Subject: [PATCH] Document the new TRO_INSERT BricsCAD command dxfmakros' TRO menu can now insert new TRO markers by hand (TRO_INSERT), not just edit ones tro_annotate.py placed; note it here since this is where the workflow and --emit-lisp switch are documented. --- doc/Python_Scripts.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/Python_Scripts.md b/doc/Python_Scripts.md index f9805ee..c0e4879 100644 --- a/doc/Python_Scripts.md +++ b/doc/Python_Scripts.md @@ -173,6 +173,14 @@ own `TRO_`-prefixed layers and carries XDATA under the app id `SPS_SKEL_TRO`; a re-run removes exactly those tagged objects (not by layer name) and rebuilds them, so hand-drawn content on the same layers survives. +Once at least one marker of a given type has been annotated, the `dxfmakros` +BricsCAD menu (`SSG_LIB > TRO`) can insert further markers of that type by +hand — `TRO_INSERT` reuses the `TRO_SYM_` block definition this tool +created and only asks for a point, an id and (optionally) a different type; +`TRO_EDIT` changes `ID`/`TYPE` on an existing marker. Neither command draws +new shapes — a type with no prior annotated instance in the drawing must be +run through this tool at least once first. + CSV and DXF live in different coordinate systems; the offset between them is handled by `dxf_registration.py` — derived once, verified on every run, and cached per CSV/DXF filename pair in `%SKEL_CFG%\dxf_registration.json` unless @@ -193,7 +201,7 @@ overridden. | `--re-register` | — | off | Re-derive the coordinate offset even if a verified one is already cached in `%SKEL_CFG%`. | | `--max-residual` | `MM` (float) | `600.0` | Largest residual error of the coordinate registration that is still accepted; above it the run fails (exit 4). | | `--check` | — | off | Dry run: only analyze and report, write no output file. | -| `--emit-lisp` | — | off | Regenerate `cad/tro_types.lsp` (the type list for the `TROEDIT` dialog) from `tro_catalog.py` and exit — no `--dxf` needed. Written under `%DXFM_LISP%` if set (next to the `dxfmakros` SSG_LIB modules that provide the dialog), otherwise under `/cad`. | +| `--emit-lisp` | — | off | Regenerate `cad/tro_types.lsp` (the type list for the `TRO_INSERT`/`TRO_EDIT` dialogs) from `tro_catalog.py` and exit — no `--dxf` needed. Written under `%DXFM_LISP%` if set (next to the `dxfmakros` SSG_LIB modules that provide the dialogs), otherwise under `/cad`. | **Output** (in `%SKEL_RESULTS%`, unless `--check`): `_annotated.dxf`, `_registration.json` (the coordinate transform used, with its proof).