36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
# BIM batch ad6d319035418df1de66f85c
|
|
|
|
Edits only. No tests, business acceptance, browser validation, benchmarks,
|
|
builds, synchronization, or route generation were performed. The outer
|
|
pipeline owns build, sync, and route receipts; these are not business acceptance.
|
|
|
|
The 16 selected commands retain the existing native document dispatch in
|
|
`BimRuntimeProbe.cpp`. Their registration comments now use the existing
|
|
single-command marker syntax. Markers do not establish desktop parity.
|
|
|
|
The mounted `BimFrameTask` now offers document inspection for every selected
|
|
command. Native inspection skips the mutation branch and recompute, returns
|
|
document objects and topology, and preserves selection. The adapter permits an
|
|
empty changed-object list for explicit inspection while retaining the existing
|
|
mutation checks. Empty optional task fields use native defaults. An invalid
|
|
explicit path fails instead of falling back to unrelated selection. Pipe resize
|
|
resets placement before replacing local geometry and restores the updated
|
|
placement afterward.
|
|
|
|
Remaining implementation boundaries observed in the supplied native handler:
|
|
|
|
- Pipes and fittings are constructed through Part/OCCT operations, but pipes
|
|
use plain features with dimensional properties rather than the optional
|
|
CommandsPipe provider's parametric objects. Editing those properties alone
|
|
is not connected to a recompute proxy.
|
|
- Pipeline creation currently creates a group of straight pipes; automatic
|
|
elbows at bends and provider pipeline regeneration remain unconnected.
|
|
- FrameLine management uses explicit task actions and ArchStructure members;
|
|
the FrameLine container has no provider recompute proxy.
|
|
- The anchored desktop InitGui imports optional CommandsFrame and CommandsPipe
|
|
modules. This batch did not establish parity with their complete interactive
|
|
workflows, fitting catalogs, or attachment semantics.
|
|
|
|
These boundaries remain open. The edits and registration markers must not be
|
|
reported as complete desktop behavior or user acceptance.
|