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=optonline.net; s=dkim-001; t=1602641100; bh=bJK5GNupo6FnA0D6rEC/SDQkRH4j7EJ9gyAfHMi/SwE=; h=From:Date:Message-ID:Subject:To; b=ekUl4KnUX76EelnYxkjEiL2uJWK8HpG/ce8b1GLumSK0NcoBCfxAPLqY3sXRf5zdz HCfeiQsJMpDiJIdfJnc3FdzoN7XtPf9Y3W1PHTA/I0awIXEeAajR6ewr2SOgr/NJun hNL6Bv6W3oe8V/MgsZm1cyII8blefXfM4WZmujvrQq7dcl/qKZJNEzbXbqA/kZufoF rE898dlwAWHwrIUCN7hSf4+6ire3LwrBSSx92IK7hHt9IdH2x8cxQZw4aAxcbKNIaM PTC3/Q2FXmWWudIf4C4Y6tKdARxLfGaQm1AMr0yH3bdhScSS5gMwV9aXuKQMbGh2FY PFHCdDi2KUQcg== Authentication-Results: mta4.srv.hcvlny.cv.net smtp.user=geneglick; auth=pass (LOGIN) Authentication-Results: mta4.srv.hcvlny.cv.net x-tls.subject="/C=US/ST=California/L=Mountain View/O=Google LLC/CN=smtp.gmail.com"; auth=pass (cipher=AES128-GCM-SHA256) X-Content-Analysis: v=2.3 cv=b4wpHuOx c=1 sm=1 tr=0 a=qClb9Ql7wM4GXenlcXDlgg==:117 a=afefHYAZSVUA:10 a=pGLkceISAAAA:8 a=Mj1Xp5F7AAAA:8 a=xRfjoxBpAAAA:8 a=-qk9OpF0jw4j7Yx9x4UA:9 a=QEXdDO2ut3YA:10 a=ClaC7e_1HWqxbknmblcA:9 a=sQVAEAfh7L4jq4K9:21 a=OCttjWrK5_uSHO_3Hkg-:22 a=4plUlNce3Gdv3FjnGo9M:22 X-Gm-Message-State: AOAM5312pCueO+tLqz9gQ8OXWrs4vxUgN64tTtdM6za18xCfigHymgXS xMdWEPHfreYeZzCLRLfVrVDRUlIXd8M8Bbx5m0I= X-Google-Smtp-Source: ABdhPJz2OV4fttDUN+ZqONvK2BnAkeW+lVNnRtJFeQ4c7o+cZDpj7QJw9mldVV9TRlylol1Zkgy6DhlxERQCdiieJcA= X-Received: by 2002:a25:d7c4:: with SMTP id o187mr3892882ybg.363.1602641094788; Tue, 13 Oct 2020 19:04:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "gene glick (geneglick AT optonline DOT net) [via geda-user AT delorie DOT com]" Date: Tue, 13 Oct 2020 22:04:45 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [geda-user] PCB DRC Riddle To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary="0000000000002849f205b197f5ab" Reply-To: geda-user AT delorie DOT com --0000000000002849f205b197f5ab Content-Type: text/plain; charset="UTF-8" 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] 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] 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 >> >> >> --0000000000002849f205b197f5ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sure, Chad. I'll send it to your direct email add= ress. Stay tuned.

Also - if I get rid of all other= errors, does that mean the default message remains? Does it say "cong= rats on no errors"?

The first item is a "default warning". I believe th= e DRC works as advertised, but it does have some limitations, as we have re= cently been discussing on the list. For example, as the warning says, the d= etection of outright shorts and other connectivity is currently part of a d= ifferent subsystem.

The second warning seems odd. = If that parameter is set to 0, I don't think it should be throwing thos= e. Is it possible to send the pcb file that is generating the warning? I= 9;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 c= om] <geda= -user AT delorie DOT com> wrote:
I am using PCB version 4.2.2 and hav= e 2 strange DRC warnings that I cannot figure out.

1. WARNING: DRC doesn't catch everything (0.00) blah blah blah Require= d 0.00
2. WARNING: DRC minimum copper overlap (0.00) blah bla= h blah Required 0.00

When clicked, both warnings m= ove the cursor to the upper left hand corner. As far as I can see, there= 9;s nothing there.

Any ideas?

=
thanks,

Gene

--0000000000002849f205b197f5ab--