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=zlTOjrzy7RP8sHyG6B8ao9b5wvS27cDGMOWt/a/bQnI=;
        b=Q+G2ny4mn+U15qS1p1vzrQSREpMRRdStEKilxO4yAPiXkUFC8hxLU7rKC8FU1n8X91
         ym4ZiQoeApZwgxbUHZ1idYsriRicGZsEnfy6hHwvjQhdWb6tjLzCgULbq/u3lFbROnBu
         FZIHtIGcCIEgafL8JI7M1mPXUcaNse0QwBQVVm3/spfOLrFWogn4Bt46P8fZhZpwuzuB
         Cs5sHVLYfPqRMKl1iVsuNo7LieXOYYD1H6XuWGIZ5fAwNSUF5UKmvyZYifts9r6Uwc4T
         Mh6u3mTwlf+3Kc1zVT9+Maw6EFeLdYWN2f/L88WusxiOJSd9wxU0aWIR5jKbnqB1XV3v
         ZSIg==
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=zlTOjrzy7RP8sHyG6B8ao9b5wvS27cDGMOWt/a/bQnI=;
        b=raSIq2YtP/4jxLV5WnmtAwcZLMdXKQbL4Pp8xJbefSNmBtuLk2aWmmnC60Mc4rcBkP
         RVuLPNiBMF5+6GraPEnmFPes/iq0wZ1SG11xMjSH09X0UcWeTwhWa71Y815zZpN40IQY
         NB2VPDf3ZZp3kiq8ygDVAlIAYLVV7MT556U8ZyVJtclruv444C3QW2paUwpcsNaFtUJ7
         NjB/PMJeZ0YVEyA2KPWsH6mOEcAyp3bcK2hpg9jLQVBuoXX8bzmJLPel5FgdqkJx/H5z
         XVLBm/1NYqI8oWSRpZdKUUS3b7WMD4qcKU//wqtcosh6FHTYITU1mTxCCsfpvy7eyJGe
         aX2A==
X-Gm-Message-State: AOAM531i7EqtqbrDFeog2EOcqgn75ivOnMEaQEMxXK+f9yAdIVImMUhN
	MwDJHcouqKlvlXG86O7fNxJqzz3HmODT5k76rLUu5i35
X-Google-Smtp-Source: ABdhPJzHLXxSgCBVXj1GUgE6ZEW3uzPSuTbVp+NF8sdBEIE5K+iktFNBbbS9Gh+P0Bte61XsBBvqor4bPoOcAjYpBO0=
X-Received: by 2002:a1f:964c:: with SMTP id y73mr4494915vkd.8.1602010592976;
 Tue, 06 Oct 2020 11:56:32 -0700 (PDT)
MIME-Version: 1.0
References: <CAGBFkM2Bja4mjn-7mt_WUcw5AHa6DLJgrZdCDp5cpauGmy6UuA AT mail DOT gmail DOT com>
 <CAC4O8c_8vT47Afr6qPo3yn4QTgZ6ot8rYJqhFrTv8zmELM9iOQ AT mail DOT gmail DOT com>
 <CAJZxidAyVxuLiUwxWz2zhTX6DVsMNr4qGOw+6EDM9c0mV5=_iQ AT mail DOT gmail DOT com>
 <CAC4O8c8T=CTEdCEmnwEj7PgV6W0MrnRNkHVAi=+0HiY2mtqqBQ AT mail DOT gmail DOT com>
 <20201005230622 DOT 38e89fe7f870c827cc424103 AT gmail DOT com> <CAJZxidCf-Ho+YG=-FvT3OxZO_1-YWuM=i-o7LhsDqtM+orEeNw AT mail DOT gmail DOT com>
 <20201006194215 DOT 5cf31fc25518b03a88cb4d80 AT gmail DOT com>
In-Reply-To: <20201006194215.5cf31fc25518b03a88cb4d80@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: Tue, 6 Oct 2020 14:56:21 -0400
Message-ID: <CAJZxidBGVP1_SKrRmq=7bzd2c_OAMYOZYNotBoLPxUcLmqXWOg@mail.gmail.com>
Subject: Re: [geda-user] PCB connect pad to plane
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary="0000000000005224a705b1052833"
Reply-To: geda-user AT delorie DOT com

--0000000000005224a705b1052833
Content-Type: text/plain; charset="UTF-8"

There are design rules for other non-copper objects that ought to be
observed. For example, distance between an object and the edge of the
board, or a hole. There's also thickness of silk screen lines, or silk
lines drawn over exposed copper.

On Tue, Oct 6, 2020 at 2:22 PM Nicklas Karlsson (
nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <
geda-user AT delorie DOT com> wrote:

> > ... I don't agree. Ideally the DRC would also be "net-aware" (aka
> > "connection-aware") so that it could have net-specific design rules, as
> > well as verifying that you haven't shorted any nets together.
>
> Yes it must be net-aware but it should only care about all copper objects.
>
> > It would be
> > nice to be able to set different clearances for high-voltage nets, or
> > different minimum trace widths for power nets, for example.
>
> Without doubt and DRC is more important than online guidance.
>
> > In terms of priorities, when I reworked the DRC I wanted to make sure
> that
> > it did what it already advertised accurately (which I believe it now
> does).
>
> That's good.
>

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

<div dir=3D"ltr"><div>There are design rules for other non-copper objects t=
hat ought to be observed. For example, distance between an object and the e=
dge of the board, or a hole. There&#39;s also thickness of silk screen line=
s, or silk lines drawn over exposed copper.</div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 2020 at 2:2=
2 PM Nicklas Karlsson (<a href=3D"mailto:nicklas DOT karlsson17 AT gmail DOT com" targ=
et=3D"_blank">nicklas DOT karlsson17 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 DOT com" target=3D"_blank">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">&g=
t; ... I don&#39;t agree. Ideally the DRC would also be &quot;net-aware&quo=
t; (aka<br>
&gt; &quot;connection-aware&quot;) so that it could have net-specific desig=
n rules, as<br>
&gt; well as verifying that you haven&#39;t shorted any nets together.<br>
<br>
Yes it must be net-aware but it should only care about all copper objects.<=
br>
<br>
&gt; It would be<br>
&gt; nice to be able to set different clearances for high-voltage nets, or<=
br>
&gt; different minimum trace widths for power nets, for example.<br>
<br>
Without doubt and DRC is more important than online guidance.<br>
<br>
&gt; In terms of priorities, when I reworked the DRC I wanted to make sure =
that<br>
&gt; it did what it already advertised accurately (which I believe it now d=
oes).<br>
<br>
That&#39;s good.<br>
</blockquote></div>

--0000000000005224a705b1052833--