Files
FreeCADWasmDev/docs/current/techdraw-annotate-boundaries.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

2.0 KiB

TechDraw Annotation Batch Boundaries

Batch: aef2c87159bdac06dfcbcec0

The four selected commands now explicitly select the existing native family route in web/src/techdraw-desktop-adapter.ts. The existing created-view response consumer also accepts decoration, Show All, and surface finish responses, but only when native success, document mutation, completed operation, matching document/page, and nonempty rendered SVG are supplied. This does not make their native implementations complete.

Remaining work:

  • TechDraw_DecorateLine: replace the incomplete branch at TechDrawDesktopCommands.cpp:421 with transactional native geometric/cosmetic edge formatting and native SVG refresh. Read the actual formatting APIs and desktop task before editing this branch.
  • TechDraw_ShowAll: replace the incomplete branch at TechDrawDesktopCommands.cpp:463 with persistent view visibility state and its renderer consumption, following CommandAnnotate.cpp:1336.
  • TechDraw_SurfaceFinishSymbols: replace the incomplete branch at TechDrawDesktopCommands.cpp:463 with native symbol creation/editing and page/view/leader attachment, following CommandAnnotate.cpp:1465 and its referenced task.
  • TechDraw_FaceCenterLine: finish inspection of the existing native creation and response branch at TechDrawDesktopCommands.cpp:2714, including its completion status at line 2896; connect matching mounted task parameters and editing semantics before adding an implementation registration.
  • Mount annotation task controls through workbench-shell.tsx:887 after confirming the corresponding native parameter contracts.

Source inspection was stopped by SCHEDULER_SOURCE_BUDGET_REACHED, including the targeted read of TechDrawDesktopCommands.cpp:2760. No implementation markers were added. No tests, acceptance, browser validation, benchmarks, historical reconciliation, builds, or synchronization were run. The outer pipeline owns incremental build/sync/route receipts; these edits are not business acceptance.