docs(spec,plan): track H states what it does with xrefs
The spec promised that the first live task would measure xrefs. It never did: the plan measures model space, paper space and block definitions. 1.6 does not read an xref's own entities on either engine; the host drawing is what gets read. The snapshot docstring and drawing_understand's docstring now say so, and nothing is claimed about the live engine that was never measured. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FKFStjEFzpGyLq5bMpWxTd
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
9b45243bdd
commit
f0c50d772f
@@ -98,8 +98,9 @@ handle, geometry, text, block name, attributes) filled once per drawing, so a
|
||||
exported too, and ezdxf read the result. The extension argument must be
|
||||
`"DXF"`; `".dxf"` fails with *Invalid argument* (measured). The snapshot goes
|
||||
to a temporary folder and is deleted afterwards. Whether paper-space content
|
||||
and xrefs reach the snapshot is measured by the plan's first live task and
|
||||
stated in the tool docstrings.
|
||||
reaches the snapshot is measured by the plan's first live task and stated in
|
||||
the tool docstrings. An xref's own entities are not read in 1.6 on either
|
||||
engine - the host drawing is - and `drawing_understand`'s docstring says so.
|
||||
- `MAX_DXF_BYTES` default rises from 50 MB to 512 MB, and the refusal names the
|
||||
size and the variable (a real layout here was 188 MB).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user