tro_annotate --read-tros: TRO-Handkorrekturen aus BricsCAD, Staubereiche vor dem TRO
- Marker tragen KEY (ID der ID-Datei) und SLOTS (Bauteil je Slot), die Zeichnung die Bauteiltabelle SPS_SKEL_PARTS (XRECORD) fuer "Im Plan waehlen" im Dialog TRO_EDIT (dxfmakros) - --read-tros schreibt geaenderte, neue und geloeschte Marker als Abschnitte edit/edit_add nach cfg/tro_overrides.ini; tro_flow.apply_edits wendet nur diese Arten an (Bauteile mit Lage, exportfest) - --emit-lisp schreibt dazu *TRO-SLOTS* und *TRO-SLOT-KINDS* - model: Lagerlinien zaehlen je TRO (Katalog nur Vorgabe), Mubea-Speicher jetzt 20 Linien (Golden-Datei) - Staubereich als stehendes graues Rechteck direkt vor seinem TRO-Marker (jam_abstand statt jam_versatz); Marker 150 mm, Text 120 mm Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -207,7 +207,12 @@ byte — rewrite them (`SKEL_UPDATE_GOLDEN=1`) only for a reviewed, intended cha
|
||||
call as `tro_flow.py`) into a copy of the DXF for a visual check in BricsCAD. With
|
||||
`--anlage <csv>_anlage.json` also the jam areas (block `JAM_AREA`, name `Jam<NNNN>_<k>`,
|
||||
double-click → dialog `JAM_EDIT` in dxfmakros); `--read-jams` takes numbers edited there
|
||||
into `cfg/<csv>_jam_names.ini`, which `scl_skeleton` applies.
|
||||
into `cfg/<csv>_jam_names.ini`, which `scl_skeleton` applies. TRO markers carry `KEY` and
|
||||
`SLOTS` (part per slot); the dxfmakros dialog `TRO_EDIT`/`TRO_INSERT` (one dialog for all
|
||||
types, rows from `*TRO-SLOTS*`, pick-in-drawing from the XRECORD `SPS_SKEL_PARTS`) edits
|
||||
them, and `--read-tros` writes the differences as `edit`/`edit_add` sections into
|
||||
`cfg/tro_overrides.ini` — the only kinds of that file `tro_flow` applies
|
||||
(`tro_flow.apply_edits`, keyed on the stable ID-file IDs).
|
||||
4. **`lib/tro_extract.py`** — **parked**: reads the annotated DXF back into the old
|
||||
`sps_skel-tro-extract-v1` JSON, which `scl_skeleton.py` no longer accepts. Not deleted, not
|
||||
extended; if drawing edits (`TRO_INSERT`/`TRO_EDIT`) are ever needed again, it should
|
||||
|
||||
Reference in New Issue
Block a user