delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Recipient: | geda-user AT delorie DOT com |
X-Original-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
d=gmail.com; s=20120113; | |
h=mime-version:date:message-id:subject:from:to:content-type; | |
bh=4Yy1JhqbzPdOnVjuIMuBanV0EMdmXBhZfiq1jGD6YcQ=; | |
b=uB4kmpU1UCDjOV/kzMipjZS0rlJ85HPf3S5YM4MYPmFuJ6LWxBQi0a2sWsjZkfd2hD | |
cxtzzfw2JjDXSBXPWGMQQlkfpQcP35JOEMx7EiHqDHAT1z5ZKpV4SgDTL9D+0tS7ZVN3 | |
hiAuyMcNEAO9f28o3pHGRj9XYhbaYB+H2DE6Ve4xKVz6tMCxPpHVuKUXdMcy64TxdXrz | |
meG6Q0klL9LD86lj9Cceh38AliGowhgW/2IxkAKWFhVRuDaQIdOKEAKw3+ZjezaibZIE | |
HQG2S2dTJYRMXKC9+e4onsobXOtpik2pmP/OZxxdHdIXpbYLSCAevL4IM2NP9pBGXuAk | |
b2RA== | |
MIME-Version: | 1.0 |
X-Received: | by 10.180.205.226 with SMTP id lj2mr1107649wic.20.1445561279244; |
Thu, 22 Oct 2015 17:47:59 -0700 (PDT) | |
Date: | Thu, 22 Oct 2015 16:47:59 -0800 |
Message-ID: | <CAC4O8c8Jtm61QCsvnzLpP2fBDqRFU4j8g4Euf19yexgyWMOM4g@mail.gmail.com> |
Subject: | [geda-user] support arcs with square ends?, ellipse segment arcs? |
From: | "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Reply-To: | geda-user AT delorie DOT com |
--001a11c25ef48cef010522baf639 Content-Type: text/plain; charset=UTF-8 I hit a small geometry bug in IsPointOnArc() and in working on it started to wonder about a couple things: * are non-circular arcs needed yet? IsPointOnArc() says its broken for them but I don't know if we care since I didn't see how to make them in the interface. But I thought I heard some talk about them recently. IIRC even e.g. the toporouter doesn't use them * do we care about arcs with square ends? They have ANYOBJECTFIELDS so could in theory have this but I don't see the point, since unlike lines they aren't used to represent pads. And it takes another check against an off-axis rectangle Fixing the the other bug in this fctn (arcs thicker than their radius) is about done also --001a11c25ef48cef010522baf639 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div style=3D"">I hit a small geometry bug in IsPointO= nArc() and in working on it started to wonder about a couple things:</div><= div style=3D""><br></div><div style=3D"">* are non-circular arcs needed yet= ?=C2=A0 IsPointOnArc() says its broken for them but I don't know if we = care since I didn't see how to make them in the interface.=C2=A0 But I = thought I heard some talk about them recently.=C2=A0 IIRC even e.g. the top= orouter doesn't use them</div><div style=3D""><br></div><div style=3D""= >* do we care about arcs with square ends?=C2=A0 They have ANYOBJECTFIELDS = so could in theory</div><div style=3D"">=C2=A0 have this but I don't se= e the point, since unlike lines they aren't used to represent pads.=C2= =A0 And it</div><div style=3D"">=C2=A0 takes another check against an off-a= xis rectangle</div><div style=3D""><br></div><div style=3D"">Fixing the the= other bug in this fctn (arcs thicker than their radius) is about done also= </div></div> --001a11c25ef48cef010522baf639--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |