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=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=fS3dnWHfAhohUYYNpvngsPzYqhNHgWtXrIGs1NMXGwg=;
        b=FmFr2mnHF6Tlegg4A1/hN2Akv3rSKynWGes103uvdONx8ngeZYG5hNOycPUJb3zKi1
         jljMa+xYrnnoBTaLyJfh3og1FIvOnKHf2pV54SWWn4IViCjzQnrq3NHIvIXQbXlSSF7B
         9jo47yPr0XDOcuIQ6xu6y31l2/TJmXM3gakqAaoM8RbwitXFU89Pije6s8tN4Iq6QObu
         +hNboEWX8ICmQnZsebCKcsmmsSIaaxvVWZVSGevtv+NThRL/YnNrQu8OGiacUHeKtsA9
         t0ZZOarpMXFubUyUo/EOJxCSg5H+FJXVM3RjsPm3Zk/TMvVDLtqRQX8F7Gotcds6YE2V
         pB/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=fS3dnWHfAhohUYYNpvngsPzYqhNHgWtXrIGs1NMXGwg=;
        b=R5Xr3NgNXti8bX/gkroQDTddVazrokpq3JdNS9p2vqJksZq6QTHggHdhQqK+fiRzkL
         9B/FE86KvHitmGZzKepNENErzlUQy2Oj01qqP9Jh7VQM7TpCVETPvWhZAQfmeyvCqk/O
         AcFupFm0ret6Zb8lDPV/zXYlPo0/h8tf3e1uJvkNg8GPhrBT7CYecFwBPjhxwBHJwaUY
         d6gPBInA79ES3XM+mFeOzEshfiXANkN0Q6B1yhtUCzGWG59/B0Ihvz5t+dfaopJ6VFp7
         xooJhgfMPN+nPQGMbaafNuMx3HMHRN5btbk1JhoEdOUmKdNO6GV5yYtYSdCoR9CROQkw
         qXlg==
X-Gm-Message-State: APjAAAWTW332MxqLS1WRZpzBXuPs/h0VvAtc6ZVpyQOW2G1Ot5VnJfuW
	bWKbIj8A7A/6PrIWUSHgYP1auDy7
X-Google-Smtp-Source: APXvYqxzLzbyv5VLMVAK2X2fUH6YjrDHIkyYJ3JCh97KrII+9gAxP3UDM6hO/6BRAnAbh4TuwXWMXw==
X-Received: by 2002:a19:ec14:: with SMTP id b20mr5308049lfa.63.1579107335404;
        Wed, 15 Jan 2020 08:55:35 -0800 (PST)
Date: Wed, 15 Jan 2020 17:55:33 +0100
From: "N (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Pcb: Automatic clearance between polygons?
Message-Id: <20200115175533.28ffccf6bd454ea7ba3f6c34@gmail.com>
In-Reply-To: <f9aa875e-4c81-2eae-689e-24ba6dc00355@linetec.nl>
References: <3721c0b4-2805-2d9f-eba0-119c9c2dd81e AT linetec DOT nl>
	<CAJZxidAFqANGm2MofmyeSVTZyRS+YCS16-JtfAidjwYHoKE0GQ AT mail DOT gmail DOT com>
	<f9aa875e-4c81-2eae-689e-24ba6dc00355 AT linetec DOT nl>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

> Hello Chad,
> 
> Op 13-01-20 om 20:40 schreef Chad Parker (parker DOT charles AT gmail DOT com) [via 
> geda-user AT delorie DOT com]:
> > Hi Richard-
> >
> > What's wrong with wide traces? The end caps?
> 
> Traces are OK for simpler shapes. The problem is that they have a fixed 
> width and (of course) do not clear pads and pins. So for a more complex 
> shape, I'd have to use a thin trace to make the outline, and then 
> 'colour it in' using lots more traces.
> 
> > What about using a large element pad for your connections instead of a 
> > polygon?
> 
> This is even less convenient, as it requires defining separate pads for 
> each situation.
> 
> For example, I have four 0.5W 0805 resistors that need as much copper as 
> possible to dissipate heat, located amidst other components. So for each 
> of these resistors, I draw two polygons covering the desired area, 
> connected to the pads by setting a zero clearance gap (Shift+K) for each 
> pad. No problems so far, as other pins, pads and traces still have 
> automatic clearance with regard to this polygon.

Have done the same on several circuit boards though.

> However, when I want to fill up the remaining space with a ground plane, 
> I need to manually steer clear of the polygons that are already present, 
> which can be quite a bit of fiddly work. Not really a problem, but 
> time-consuming all the same. It would be nice if a polygon had a 
> 'clearance gap' parameter that would make other polygons observe a 
> certain clearance, just as they do with all other elements.

I do not consider it a large problem but. Guess the correct method is a flag to tell others may cut a clearance thru polygon or the opposite.


Interestingly enough  it would be possible to use flag on traces to get necking then routing thru narrow passages but then it would have problem clearing polygons. Do not think necking is common nowadays, have only rarely seen on old boards with round pins.