mirror of
https://github.com/storytold/cadcraft.git
synced 2026-10-30 13:56:46 -06:00
42667d1332
* ELLIPSE from axis endpoints matches what AutoCAD stores Typed ELLIPSE input was checked against AutoCAD 2024 black-box (synthetic input in accoreconsole, read back with entget); three rules differed: - The major axis pointed at the second axis endpoint; AutoCAD points it at the first. A full ellipse looks the same, but an elliptical arc's angles are measured from that axis, so the arc was drawn on the opposite side of the center, and the stored major vector, start point and quadrant order all differed. - A point at "Specify distance to other axis" gave its distance from the first axis; AutoCAD takes its distance from the center (the rubber band), then swaps the axes when it is the longer one. - The end-angle prompt had no Included angle option, so `_I` was rejected and the next number became an absolute end angle. AutoCAD adds the included angle (default 180) to the start angle. The JSON form (ellipse.axis / ellipse.arc with p1, p2, p3) follows the same rules. The regression test pins ten AutoCAD-measured cases, among them survey (VN-2000) coordinates, a near-millimetre ellipse and both Included angle cases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: geometry parity says which part was measured against AutoCAD The "How this was measured" section still said no numeric comparison against AutoCAD had been run, next to the new ELLIPSE revision row that reports one. It now names the 11 measured ELLIPSE cases and the test that pins them, and keeps the rest of the document marked as read from the source. Pointed out in review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ellipse: drop the import the axis-endpoint change left unused --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Brandon Thomas <echelon@gmail.com>