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:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=adNDMRPkz9uMkNNUgcWrglisnsGrcWNaNLSK4ZCws38=;
	b=ZORk+zkuFbcc4aTSxkMBUFjMc0ZuwKqVPTi9zzup+aacyCwkOEtZ28e2pxgF1QiyiQ
	5N9fCDUnVKLuAb5IBZ67uUVSQSE+WV79LmGcJ1uqYwNQmcZaKi7IXGmZlf/2yCwFBlgz
	CPnCdp9FI87L97KieDrNJP3j2GQ+v21w2ne39Pg9I2sJbBGLalaLwMhR3HPoEGuDLXAB
	qhHoDE7My43vwZJjsRHB1tpCEGLLPBZqsDMNrUOS2eVlQEB5M1hXSBykLfWG06UzF9zH
	Yy5dXjyHhIL+MoIt5dZgjn+wd2NAWjE8+pKAv8qymkTl0RRqvhreFKTOpe5ZKQUQ03oa
	dOTw==
MIME-Version:	1.0
X-Received:	by 10.194.8.227 with SMTP id u3mr22680662wja.38.1443912375213;
	Sat, 03 Oct 2015 15:46:15 -0700 (PDT)
In-Reply-To:	<560F9AC7.3040607@jump-ing.de>
References:	<CAC4O8c_kjtsHhyjH+fPZvhDdPxc+Z+L5RxPy4SpJ8dmcGNKMiA AT mail DOT gmail DOT com>
	<560F9AC7 DOT 3040607 AT jump-ing DOT de>
Date:	Sat, 3 Oct 2015 14:46:15 -0800
Message-ID:	<CAC4O8c8i3xswKjACqGR5=7siEZXU7ZH6Cj_0SoBenB-yn8kCjQ@mail.gmail.com>
Subject:	Re: [geda-user] making DRC less misleading in the presence of shorts,
	non-routed rats, etc.
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
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--047d7b5d9c0736261f05213b0ce3
Content-Type: text/plain; charset=UTF-8

On Sat, Oct 3, 2015 at 1:07 AM, Markus Hitter (mah AT jump-ing DOT de) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> Am 03.10.2015 um 01:21 schrieb Britton Kerin:
>
> > At the moment DRC catches near-shorts (trace too close to another), but
> is
> > completely silent when there's an actual short.
>
> That's expected, that's what DRC does. Checking for shorts means to
>

When I started, it was not at all expected.  Its weird that you can go from
almost-short, to short, and thereby make a violation vanish.  In fact it's
pretty easy to accidentally create a short while fixing a proximity
violation.  I happened to catch it before ordering the prototype boards but
only

--047d7b5d9c0736261f05213b0ce3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sat, Oct 3, 2015 at 1:07 AM, Markus Hitter (<a href=3D"mailto:mah AT ju=
mp-ing.de">mah AT jump-ing DOT de</a>) [via <a href=3D"mailto:geda-user AT delorie DOT co=
m">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"mailto:geda-=
user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><span class=3D"">Am 03.10.2015 um 01=
:21 schrieb Britton Kerin:<br>
<br>
&gt; At the moment DRC catches near-shorts (trace too close to another), bu=
t is<br>
&gt; completely silent when there&#39;s an actual short.<br>
<br>
</span>That&#39;s expected, that&#39;s what DRC does. Checking for shorts m=
eans to<br>
</blockquote><div><br></div><div style=3D"">When I started, it was not at a=
ll expected.=C2=A0 Its weird that you can go from almost-short, to short, a=
nd thereby make a violation vanish.=C2=A0 In fact it&#39;s pretty easy to a=
ccidentally create a short while fixing a proximity violation.=C2=A0 I happ=
ened to catch it before ordering the prototype boards but only=C2=A0</div><=
/div></div></div>

--047d7b5d9c0736261f05213b0ce3--

- Raw text -