Files
FreeCADWasmDev/docs/current/bim-archutils-batch-8a630fd083fb795bd43f7da8.md
wangdequan 9a7c4f0335 Save FreeCAD Web workspace sources and user validation evidence
IFC native binding remains incomplete; preserve accurate test results.
2026-09-15 22:01:58 +08:00

36 lines
2.0 KiB
Markdown

# BIM Arch utilities batch
Selected commands: Arch_Add, Arch_Check, Arch_CloneComponent, Arch_CloseHoles.
The existing runtime invokes BimArchUtils desktop command classes against the
requested native document and selection. The existing dispatcher validates the
BIM adapter response and applies the returned selection; the workbench consumes
the document state and Check diagnostics.
This edit removes the adapter-only failure for unchanged Add, Clone Component,
and Close Holes results. Their desktop implementations can return normally
without altering the document. It also serializes native shape validity,
closure, and solid/shell/face counts for the four selected commands, validates
those fields in the BIM adapter, and displays them in the mounted object table.
Geometry remains owned by FreeCAD/OCCT.
## Remaining boundaries
The mounted Arch_Add object view now provides an explicit host selector.
The BIM adapter moves the chosen host to the end of the selection, as required
by BimArchUtils.Arch_Add.Activated, preserving entries and their subelements.
Changing the host clears the JSON selection override so the next dispatch uses
that ordering. Native grouping and geometry behavior remain source-owned.
This control still requires browser acceptance with a native BIM document,
including a space-boundary face selection and changing hosts before Add.
Build, sync, and acceptance are deferred to the outer pipeline. No runtime or
business acceptance was executed in this edit batch. In particular, actual Add
host branches (component, space boundary, IFC aggregation, and cell merge),
clone links and autogroup, Check diagnostics and selection, and open-shape repair
still require native input/result acceptance. Existing provider availability
and native document ownership requirements remain in force. The displayed
topology summary is not proof that a repair or grouping operation changed an
object; unchanged desktop outcomes are valid and must be distinguished by
business assertions using the supplied input and resulting document.