cvs.gedasymbols.org/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
Date: | Mon, 7 Jul 2014 14:00:38 -0400 |
Message-Id: | <201407071800.s67I0cQb030511@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
In-reply-to: | <53BACBEA.1080302@sonic.net> (message from Dave Curtis on Mon, 07 |
Jul 2014 09:33:46 -0700) | |
Subject: | Re: [geda-user] pour clearing around pads |
References: | <53B8CC66 DOT 2080909 AT sonic DOT net> <201407060516 DOT s665GVb3027395 AT envy DOT delorie DOT com> <20140707064133 DOT GA3710 AT visitor2 DOT iram DOT es> <53BACBEA DOT 1080302 AT sonic DOT net> |
Reply-To: | geda-user AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-user AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> I'm not sure where to look for how a zero-thickness pad might cause > phantom shorts or how it interacts with route blocking. Clues welcome. The code considers a pad to be a line segment between two points, and may do a "do these segments intersect" test independent of the "check the width" test. djopt, I think, does this - intersection of segments is a different test than the "happen to touch due to width" test.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |