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
	:content-transfer-encoding;
	bh=nhTq3qOgDPnEBDopf+OcxZ3G/tzuXutCjOnUkrYuaO0=;
	b=SN7qcz1qWOq8xKjWCtFmg7WFBep0h/eARFw3hR/02Mwg+SwfMPvc8RBlNGUjkO3onO
	VOcEn9oj7kMjuxbCwtdEV5wpwZemIoepS3jvVQZLXXzA6X9vycwZvfxrsmrRUNdp+uEJ
	EK/uuAgWBNiPfuaQ126lGs2G0VDvcUZDLx4Z+/9HFaabx4eYX/pho3Gv0AfvbQz67fdj
	oWxUAoHPTuzsVCnFiTHxQjFJNPgruB9KZWSYLsVpaQP2t90MfqeafLBXz83euxvRDQhG
	l/+XE+hVI4xZp8a9IMUuDUr98vwaAIXcwHca99B+y8dJS5dbu3X7KPGdvUXgHEyOsLUC
	1W2w==
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:content-transfer-encoding;
	bh=nhTq3qOgDPnEBDopf+OcxZ3G/tzuXutCjOnUkrYuaO0=;
	b=orx+uOXqRZc3qobZrgrP/fiWZHNNrPBMy6c2HoNSwKmxJGIY1MaCY8rYWmbQLViutP
	KqFWUUx0swsCACRRRx1PmMO9T7VoQr24P6tzTgOjt6TNQc1dHGosrF3t4zpw2dQc4QLZ
	zQ5zqZMEnd/yuRHHwQ5nbpZERIsj6xMJ9IA8iBfUeeaG6rQ9tl/uBAW9mTNug8O+gydG
	6E7IkVQrBPZSGGBN6uBnmKKhUGMlpmq8zXTqEbdbuvHS4qdXNhLD0b8BDoGahhePwlQl
	lKrvesUccNrTzKqPXWQLtVqmdkFoYJfHVOyHPfuhPqSRv9zbzaIkZkpN2S+GbjHjJmkP
	opGw==
X-Gm-Message-State:	AOAM530Gh5S1YmxjdsxvU9+q1CGVa58IncQvrXp6PDaiZp9CpcICXPr6
	SqtoKUPVlYj10u8py2Wp71HoZ7FGKbmERpeb5tbKWtW2XE0=
X-Google-Smtp-Source:	ABdhPJx78urnIZ/i+BXRW1XvaguCwFlY4WKsTbTRaiW9FIqRZAWmBUn4fMJiDWtjVSvX9JKKE1boH+dO2Cvx+EpWOwI=
X-Received:	by 2002:a25:bd52:: with SMTP id p18mr2605533ybm.94.1601927889662;
	Mon, 05 Oct 2020 12:58:09 -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>
In-Reply-To:	<CAJZxidAyVxuLiUwxWz2zhTX6DVsMNr4qGOw+6EDM9c0mV5=_iQ@mail.gmail.com>
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Mon, 5 Oct 2020 11:57:58 -0800
Message-ID:	<CAC4O8c8T=CTEdCEmnwEj7PgV6W0MrnRNkHVAi=+0HiY2mtqqBQ@mail.gmail.com>
Subject:	Re: [geda-user] PCB connect pad to plane
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 095JwdCt009637
Reply-To:	geda-user AT delorie DOT com

On Mon, Oct 5, 2020 at 6:40 AM Chad Parker (parker DOT charles AT gmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
> If you set the clearance of a pad to zero inside a polygon, you should get a "Pad with insufficient clearance inside polygon" error, not a "copper areas too close error". If you're getting the latter, that's a bug and we should fix it. Are you building from source? Have you run the tests? The DRC now has a pretty comprehensive set of test cases, and I would expect this to be flagged. A quick test with 4.2.0 on Win10 flags this correctly.

It's the insufficient clearance one

> It should, however, throw an error. It is technically breaking a design rule, even if you're doing it intentionally. The consequences of making such a connection unintentionally is quite high, and so it's safer, IMO, to throw the error and have you verify that the connection is intentional.

thinking about the overall issue for more than half second I agree.
It happens to work out well for ground plane and ground pads but there
are other cases.  This is sort of another issue that comes up because
DRC and connection are sort of unaware of each other I guess.

> Yes... we need more flexibility here. I'm aware. Also, SM pad thermals are high on my priority list, the availability of which I would expect to make this a non-issue.

Wouldn't this have the same problem that if you move the element onto
a non-ground poly it will short?

Britton

- Raw text -