Tool count 131 -> 154; 474 -> 1242 collected tests. The release exists for two measured reasons. A 149-tool catalog costs a client ~40,300 tokens before it has asked for anything, and a drafter searching the way drafters think -- FILLET, BPOLY, QSELECT, WBLOCK -- scored df=0 against the stock index, because those words were simply not in the data. Discovery and batching - DISCOVERY_MODE=search replaces the catalog with search_tools + call_tool, ranked over an AutoCAD command and synonym corpus (discovery/aliases.py) on top of fastmcp's BM25 index. Measured: 40,305 -> 356 tokens advertised. - cad_batch runs a step list in one round trip; fields= projects result-heavy responses. The `core` profile is gone -- discovery replaced it. Honesty debt (Tier 0) - OCS/ECS: `extrusion` appeared nowhere in this codebase, so mirrored and rotated geometry reported coordinates that were quietly wrong. backends/ocs.py translates at the backend boundary; every tool coordinate is WCS on both engines, and a tilted plane refuses rather than answering with a number that looks fine. - drawing_save_as(fmt="dwg") wrote DXF bytes to a .dwg path. drawing_audit never repaired. analysis_measure_area shoelaced points the caller typed in. - ezdxf calls gained a per-call timeout, so one hung call can no longer wedge a server whose document lock is a single asyncio.Lock. Architecture - The 1854-line backend ABC is 19 contract modules; @capability(key, reason=) makes optional methods declarative and a gate fails on undeclared holes. - 8 layout/viewport tools, CHSPACE, CAD_PROGID escape hatch. - Wave A: selection filters, boundary tracing, hatch depth, annotation objects, measurement -- 13 tools of a planned 39. The REGION and 2D-boolean family was cut on evidence: add_region() yields zero ACIS bytes and the greiner_hormann substitute loses 28.2% of the area on a square with one semicircular edge. Verified against a live AutoCAD 2026, which found four COM defects no amount of reading would have caught -- AcadPViewport has no ViewCenter, and the line that set it had been swallowed by a bare except since v1.4. Benchmark v3 (15 tasks) and what it caught - v2 scored this server 10/10, which carried no information: every task in it exercised something the server was built around. Five tasks were added because they can fail, and three did while being written -- a hatch could not be measured though the refusal listed HATCH as measurable, the boundary tools and the measure tool disagreed about the same shape (139.2177 vs 139.2699), and a circle stored as two bulged vertices measured 0.0. - Competitor reports are NOT re-scored. They are pinned v1.4 runs against v2 and were never asked these five questions; the chart shows those rows `not run`. - Correctness A/B: 21/24 -> 24/24, zero regressions. Performance, stated plainly The published v1.4 perf report was recorded on CPython 3.14 and the new one on 3.11.15, so the apparent 2-6x speedup is the interpreter, not this release. Re-measured on one interpreter, v1.5.0 is 28% slower creating entities and 22% slower on the 10k roundtrip. Fully attributed: EZDXF_CALL_TIMEOUT=0 restores v1.4.0's exact numbers. That is the deadlock fix being paid for, the knob is documented, and winning it back is on the 1.6 roadmap. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
126 lines
3.5 KiB
Python
126 lines
3.5 KiB
Python
"""Moving, copying and editing geometry.
|
|
|
|
Split out of the single 1854-line ``AutoCADBackend`` ABC in v1.5.0 (M7).
|
|
``AutoCADBackend`` composes every contract in this package, so importing
|
|
``backends.base.AutoCADBackend`` is unchanged for callers.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from abc import ABC, abstractmethod
|
|
from typing import TYPE_CHECKING
|
|
|
|
if TYPE_CHECKING:
|
|
from backends.base import EntityInfo
|
|
|
|
|
|
class EntityModificationContract(ABC):
|
|
@abstractmethod
|
|
async def entity_move(self, handle: str, dx: float, dy: float, dz: float = 0.0) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def entity_copy(
|
|
self, handle: str, dx: float, dy: float, dz: float = 0.0
|
|
) -> EntityInfo: ...
|
|
|
|
@abstractmethod
|
|
async def entity_rotate(
|
|
self,
|
|
handle: str,
|
|
base_x: float,
|
|
base_y: float,
|
|
angle_deg: float,
|
|
) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def entity_scale(
|
|
self,
|
|
handle: str,
|
|
base_x: float,
|
|
base_y: float,
|
|
factor: float,
|
|
) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def entity_mirror(
|
|
self,
|
|
handle: str,
|
|
x1: float,
|
|
y1: float,
|
|
x2: float,
|
|
y2: float,
|
|
delete_original: bool = False,
|
|
) -> EntityInfo: ...
|
|
|
|
@abstractmethod
|
|
async def entity_offset(
|
|
self,
|
|
handle: str,
|
|
distance: float,
|
|
side_x: float | None = None,
|
|
side_y: float | None = None,
|
|
) -> EntityInfo: ...
|
|
|
|
@abstractmethod
|
|
async def entity_delete(self, handle: str) -> dict: ...
|
|
|
|
@abstractmethod
|
|
async def entity_array_rectangular(
|
|
self,
|
|
handle: str,
|
|
rows: int,
|
|
cols: int,
|
|
row_spacing: float,
|
|
col_spacing: float,
|
|
) -> list[EntityInfo]: ...
|
|
|
|
@abstractmethod
|
|
async def entity_array_polar(
|
|
self,
|
|
handle: str,
|
|
count: int,
|
|
fill_angle: float,
|
|
center_x: float,
|
|
center_y: float,
|
|
) -> list[EntityInfo]: ...
|
|
|
|
# ── text annotation (M8 / F15) ───────────────────────────────────────────
|
|
|
|
@abstractmethod
|
|
async def text_set_background(
|
|
self,
|
|
handle: str,
|
|
enabled: bool = True,
|
|
color: int | None = None,
|
|
scale: float = 1.5,
|
|
) -> dict:
|
|
"""Put an opaque background box behind an MTEXT. ``{ok, handle, enabled}``.
|
|
|
|
MTEXT only — TEXT has no background-fill attribute, so setting one on
|
|
it would report success and change nothing. ``scale`` is a multiple of
|
|
the text box and must be >= 1: a box smaller than its text is a stripe
|
|
through the text, not a mask.
|
|
"""
|
|
...
|
|
|
|
@abstractmethod
|
|
async def text_find_replace(
|
|
self,
|
|
find: str,
|
|
replace: str,
|
|
layer: str | None = None,
|
|
match_case: bool = True,
|
|
dry_run: bool = False,
|
|
) -> dict:
|
|
"""Replace text across the drawing.
|
|
|
|
Returns ``{ok, replaced, entities, searched_types, note, dry_run}``.
|
|
``searched_types`` is reported rather than assumed: "no matches" and
|
|
"that type was never searched" are different answers, and an editor
|
|
that silently skips block attributes is the classic version of this
|
|
bug. DIMENSION text is deliberately out of scope — its ``text`` field
|
|
holds the ``<>`` override placeholder rather than the measurement, so
|
|
editing it would either do nothing or break the association.
|
|
"""
|
|
...
|