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=20161025;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
	bh=EZBCliDg31wz0LzM2ltD8BLSMqoHemx2DZBtSMxwy3Q=;
	b=qtAdR3Ht77Ct565JKDKcY/MFOT0nbH6qP3/Hv3iLrX4xAhUGAd+TAMf6e2qKATE51j
	2XhicphaAz7MttKotl46X0DrDjx557sczy65dTKASO2ouoz/XzMYD9P0HVb5WnEtqcro
	cZ1aknh/lZ9gRc7czsKd9WIcI23JFK5qW41B5aooct6R30HDq9mIdTnBDm3iBjSnZFma
	P4tcSZ7rHU155+HvjP8ODpGwDQs7/TkLi9N8GHAurQtB2rgdDeueQQLa1nNrloepj4tG
	jZUpHy2yawORU5cN6D/NOB4sRpOa0OSp+/xbIYCNHXMFjGtknuLeAosmorQ5lwu7mmBB
	htyA==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=EZBCliDg31wz0LzM2ltD8BLSMqoHemx2DZBtSMxwy3Q=;
	b=BRjPYvj1HePdSLOlcGtQug+fnhuaD9X/amuiBdrCk4lfctnMT1gh9VAX3ZohlpTf8F
	jMR8pMER5tEiN+BRqiP/eksOeHF7VPDEYL5jpwOVldyvu8iEbW964KDIJECFSh+AYd3W
	UQfJ0Swdsf4lqmPK3oiPHJ35ybMuhC6PtMReOlsX24O11uXkxgYMXJGzcctPDnBo0uDL
	+HTSw0i00zFZ065OrjQ2pRafhe84pwffPLR6A1CfmOoW3r458SAtxNFQCMIWrxs/n/Gn
	WOoFSZXreBy0BKFEPeEl5E3rbUniu7kIoQkYO/DMZcnRt5yS1sfQvNpKmQYXAfawFAuv
	F3Rw==
X-Gm-Message-State:	AOAM531s9G+b+A6x+h3GlI8jWeYq4/RMfAQ6PdX/DkXU5b7mNTMJpsX8
	p5d2Fl9Gn0y3q8qrVKFe3RNtRB1VACPW03JUbsPWbP8M
X-Google-Smtp-Source:	ABdhPJznpy1s2eRKz4E5o1sDnC+L/TAG78L7KLlpW6XmcZIThG36ZajVkHEwxcsirZAp1AFOdBbYxZeKuK0EhZsThTI=
X-Received:	by 2002:ab0:3a92:: with SMTP id r18mr3134977uaw.42.1602684257071;
	Wed, 14 Oct 2020 07:04:17 -0700 (PDT)
MIME-Version:	1.0
References:	<CAGBFkM3wYaxCR8_WmU6NGyb1AL9A2tMDsV0c6qwNzi+-AXW3Mw AT mail DOT gmail DOT com>
	<CAJZxidDGyx4R+nuJNs6msYnTixqaaQpzQuqj1ys3J_YQH2AxMw AT mail DOT gmail DOT com> <CAGBFkM1NMuW4Koqq=kidNzRLnnLS4TYfTwJdSquAiNerA_PpYw AT mail DOT gmail DOT com>
In-Reply-To:	<CAGBFkM1NMuW4Koqq=kidNzRLnnLS4TYfTwJdSquAiNerA_PpYw@mail.gmail.com>
From:	"Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Wed, 14 Oct 2020 10:04:06 -0400
Message-ID:	<CAJZxidBLNgsuVW6YT1XGh-c6gaeVpb0n7rpbOuCZh2iZhLrL6w@mail.gmail.com>
Subject:	Re: [geda-user] PCB DRC Riddle
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

--000000000000d47c1705b1a20133
Content-Type: text/plain; charset="UTF-8"

Thanks, received. I'll have a look at it.

Yes, the default message will still remain even if there are no violations
detected. Perhaps a congrats message would be in order :)

--Chad

On Tue, Oct 13, 2020 at 10:43 PM gene glick (geneglick AT optonline DOT net) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> Sure, Chad. I'll send it to your direct email address. Stay tuned.
>
> Also - if I get rid of all other errors, does that mean the default
> message remains? Does it say "congrats on no errors"?
>
> On Tue, Oct 13, 2020 at 9:51 AM Chad Parker (parker DOT charles AT gmail DOT com)
> [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> The first item is a "default warning". I believe the DRC works as
>> advertised, but it does have some limitations, as we have recently been
>> discussing on the list. For example, as the warning says, the detection of
>> outright shorts and other connectivity is currently part of a different
>> subsystem.
>>
>> The second warning seems odd. If that parameter is set to 0, I don't
>> think it should be throwing those. Is it possible to send the pcb file that
>> is generating the warning? I'll take a look at it.
>>
>> Thanks,
>> --Chad
>>
>> On Mon, Oct 12, 2020 at 9:26 PM gene glick (geneglick AT optonline DOT net)
>> [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>
>>> I am using PCB version 4.2.2 and have 2 strange DRC warnings that I
>>> cannot figure out.
>>>
>>> 1. WARNING: DRC doesn't catch everything (0.00) blah blah blah Required
>>> 0.00
>>> 2. WARNING: DRC minimum copper overlap (0.00) blah blah blah Required
>>> 0.00
>>>
>>> When clicked, both warnings move the cursor to the upper left hand
>>> corner. As far as I can see, there's nothing there.
>>>
>>> Any ideas?
>>>
>>> thanks,
>>>
>>> Gene
>>>
>>>
>>>

--000000000000d47c1705b1a20133
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks, received. I&#39;ll have a look at it.</div><d=
iv><br></div><div>Yes, the default message will still remain even if there =
are no violations detected. Perhaps a congrats message would be in order :)=
</div><div><br></div><div>--Chad<br></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 13, 2020 at 10:43 PM =
gene glick (<a href=3D"mailto:geneglick AT optonline DOT net">geneglick AT optonline.=
net</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT co=
m</a>] &lt;<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div>Sure, Chad. I&#39;ll send it to your direct email addre=
ss. Stay tuned.</div><div><br></div><div>Also - if I get rid of all other e=
rrors, does that mean the default message remains? Does it say &quot;congra=
ts on no errors&quot;?<br></div></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 13, 2020 at 9:51 AM Chad Parker=
 (<a href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank">parker.char=
les AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"=
_blank">geda-user AT delorie DOT com</a>] &lt;<a href=3D"mailto:geda-user AT delorie.=
com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>The first=
 item is a &quot;default warning&quot;. I believe the DRC works as advertis=
ed, but it does have some limitations, as we have recently been discussing =
on the list. For example, as the warning says, the detection of outright sh=
orts and other connectivity is currently part of a different subsystem.</di=
v><div><br></div><div>The second warning seems odd. If that parameter is se=
t to 0, I don&#39;t think it should be throwing those. Is it possible to se=
nd the pcb file that is generating the warning? I&#39;ll take a look at it.=
</div><div><br></div><div>Thanks,</div><div>--Chad<br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 12,=
 2020 at 9:26 PM gene glick (<a href=3D"mailto:geneglick AT optonline DOT net" tar=
get=3D"_blank">geneglick AT optonline DOT net</a>) [via <a href=3D"mailto:geda-use=
r AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] &lt;<a href=3D"=
mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr"><div>I am using PCB version 4.2.2 and have 2 strange DRC warning=
s that I cannot figure out.</div><div><br></div><div>1. WARNING: DRC doesn&=
#39;t catch everything (0.00) blah blah blah Required 0.00<br></div><div>2.=
 WARNING: DRC minimum copper overlap (0.00) blah blah blah Required 0.00</d=
iv><div><br></div><div>When clicked, both warnings move the cursor to the u=
pper left hand corner. As far as I can see, there&#39;s nothing there.</div=
><div><br></div><div>Any ideas?</div><div><br></div><div>thanks,</div><div>=
<br></div><div>Gene<br></div><div><br></div><div><br></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000d47c1705b1a20133--

- Raw text -