10. DXF export layer table

⚠ Known defects

This item's subject has a known defect in the code. Source: cadmaster/defects.json → cadmaster/KNOWN_DEFECTS.md, not this page — the text below is generated from the register so the two can never disagree.

• D14 — The DXF parser reads BLOCK-definition geometry at block-local coordinates, ignores the INSERT that places it, and reports nothing skipped (DEFERRED)
  dxf_io.parse walks the whole group-code stream and dispatches on six entity types -- POLYLINE, LWPOLYLINE, LINE, ARC, CIRCLE, SPLINE (dxf_io.py:113-244). It does not track SECTION, so a LINE sitting in the BLOCKS section is picked up exactly as if it were in ENTITIES, at its block-local coordinates. The INSERT that positions, scales and rotates that block is not an entity it knows, so it falls through the loop's trailing `i += 1` and is discarded. Every other entity type does the same: ELLIPSE, HATCH, SOLID, TEXT, MTEXT, DIMENSION, LEADER, 3DFACE, POINT, ATTRIB. There is no count of what was skipped and no warning.
  Cost today: None measurable on any file cut so far -- every DXF we hold uses LWPOLYLINE only. The exposure is entirely on files we have not yet been given, which is precisely what the input survey exists to find out.
  Verified: 2026-08-04. Probe written and run (cadmaster/probe_entities.py). CONTROL: the novi customer file parses unchanged at 91 polylines / 0 lines / 0 arcs / 0 circles / 0 splines, so this is a gap in coverage, not a regression. Entity list read off the code's own branches, not assumed. NOT YET RAISED WITH ARISTIDE OR JORDAN, and no fix attempted -- the phase rule says define first, and the first question is which of these entity types actually arrive from their customers, which only they can answer. DEFERRED by Jordan 2026-08-04, in his words: "Write it down as out of scope for now, but let's revisit this as part of our beta testing once the interface has been written." So this is closed to work and open on the record -- nobody should now go and fix it, and it must not be re-raised from the numbers. The revisit trigger is beta testing with real customer files arriving through an interface, which is also the only way to learn which of these entity types actually turn up. Written up for a reader on pin 14f, including a plainer explanation of the block/INSERT example, which Jordan reported was not clear the first time.