2.1 KiB
2.1 KiB
TechDraw batch c02a2bd74714fee37dfed185
Edits
- Removed the duplicate adapter guard requiring two selection objects for Dimension, ExtentGroup and HorizontalExtentDimension. The earlier current-document selection guard remains; geometry suitability belongs to the native command.
- FaceCenterLine creation now requests SVG through the existing native TechDraw.viewPartAsSvg API before committing. Rendering errors abort the transaction. The result carries document, page, view, SVG and mutation flags consumed by techDrawCreatedView and the mounted shell display.
- The shell retains the displayed drawing when a TechDraw command produces no replacement SVG, including errors and cancellation.
Remaining boundaries
- DecorateLine still returns implementation_required. Native geometric and cosmetic format persistence, task editing and formatted edge rendering remain required.
- FaceCenterLine edge-based editing still returns implementation_required. Face creation is connected to the existing SVG renderer, but centerline inclusion and formatting in that renderer have not been established in this edit. No implementation marker was added.
- ShowAll still requires persistent view-provider-equivalent visibility state and its renderer consumption.
- SurfaceFinishSymbols and WeldSymbol still require native task creation/editing, attachment semantics and rendered output.
- Dimension, ExtentGroup and HorizontalExtentDimension no longer hit the contradictory two-object adapter restriction. Their complete native routing, automatic geometry choice, extent semantics and mounted dimension output remain unresolved here. The generic C++ dimension table must not be treated as proof of those workflows: it assigns Distance/DistanceX without implementing their complete desktop behavior.
- Selected-command registration remains incomplete. Add markers only alongside completed native command behavior; do not register the remaining validation-only or implementation_required branches.
No builds, tests, business acceptance, browser validation, benchmarks or historical reconciliation were run. The outer pipeline owns build/sync/route receipts. These edits are not business acceptance.