Why: McMaster (and most AutoCAD) DXFs put the title-block template — and sometimes part geometry — inside BLOCK definitions referenced by INSERT entities. SwiftDXF has no INSERT case, so block-nested geometry is invisible (and the title block can't be cleanly identified/dropped).
Ask: parse the BLOCKS section (named block definitions = lists of entities) and INSERT entities (block name + insertion point group 10 + scale 41/42/43 + rotation 50). Provide flattened geometry: each INSERT expands to its block's entities transformed by the insert's translate/scale/rotate, tagged with the block name (so a consumer can keep or drop e.g. the title block). Nested INSERTs should recurse. Column/row arrays (70/71) can be a follow-up. Validate against ezdxf flattening of the same files.
Why: McMaster (and most AutoCAD) DXFs put the title-block template — and sometimes part geometry — inside BLOCK definitions referenced by
INSERTentities. SwiftDXF has noINSERTcase, so block-nested geometry is invisible (and the title block can't be cleanly identified/dropped).Ask: parse the
BLOCKSsection (named block definitions = lists of entities) andINSERTentities (block name + insertion point group 10 + scale 41/42/43 + rotation 50). Provide flattened geometry: each INSERT expands to its block's entities transformed by the insert's translate/scale/rotate, tagged with the block name (so a consumer can keep or drop e.g. the title block). Nested INSERTs should recurse. Column/row arrays (70/71) can be a follow-up. Validate against ezdxf flattening of the same files.