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=googlemail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
	bh=crOKiglUesXypW8+2XDp4VT2/wQ1daTDCK53JaUSkmQ=;
	b=owPn4UrF0vPGrmk5UyWRNKhhPakVMKzZCjrmUY2MIkOYlL2BYUpf/mozfSRWrqxjc0
	5woJAfHs1FJ17yliaVlun+77Fwxr1ylWc82ZeoEepryUJ06UMhzZK/hs0ETLzd+qQmRj
	XpF6hXpRvs8FaUP+3cIrfgz3Yj4Rzysl+wamzM1YaXjwuedxxMMqA+3eot8uG3MHJHds
	0+XymXFmWvUQwQTweHD4W/Q+AYDTbTyCswm62BU48EZAccZ1/6PoKKU6d9p0w0IPT2tJ
	IWS3j4I5Hk2U6JJpHm4htkWX6SZijqr/Laqs+Riy7XA8iRgsHS2cnb3xXPkS5zeAvxB2
	WTSg==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=crOKiglUesXypW8+2XDp4VT2/wQ1daTDCK53JaUSkmQ=;
	b=t9rC4wsa6KgiVjU19+9TNb7t0xqTKwH6FS0jjHX2PJyenbkIc8lm+ISK+Qlu51z9Fy
	0YYloOjYDEB+n9d3KJrasYq+7EkrgqPe9PiOFlMdzAVJEJdQfpzisrCUG1kvm0LMpsUR
	eYG1FUm/0HhKaHiFzSBja81uPF/r7/If8SvPB5gINjE8u7p3L65YQM90zGuBtA/nk0lo
	01TG4tg/elfXpwgkAGzlC25oflxyxwopdtTfsN2SJyZEPtlrzr35cznhHR93dExcxFRD
	LucCqymFAlBmAG2uBuCvF/2KVlkoWdYswi20k+B5D2shbme440M5nGorYZKAYjwVQONU
	7GHA==
X-Gm-Message-State:	AIkVDXJNA6BlOav2i1eeuRMVgMmToez2XriHdkveFLBIVdJz1ySMbCJ/Yds3kP2jNea5YMOsUbRR4fst5Fq3Qg==
X-Received:	by 10.200.41.198 with SMTP id 6mr2611643qtt.130.1484741524120;
	Wed, 18 Jan 2017 04:12:04 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<CADL2oCULu3OB9VzKpmGK=sk942JU6QuTcY9FwZPJO4zvHkgUdQ@mail.gmail.com>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1701180741180 DOT 7286 AT igor2priv> <alpine DOT DEB DOT 2 DOT 00 DOT 1701180813230 DOT 7286 AT igor2priv>
	<CAJXU7q-8_Reh8evmpD4uJkmDShbDdOZu=cQ3dsupvjdDonoerA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1701181134510 DOT 7286 AT igor2priv> <CAJXU7q8O1rdOjsEhcEVn=2xctWNuHHmDfSz+J4rWVPb0NFXULw AT mail DOT gmail DOT com>
	<CADL2oCULu3OB9VzKpmGK=sk942JU6QuTcY9FwZPJO4zvHkgUdQ AT mail DOT gmail DOT com>
From:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Wed, 18 Jan 2017 12:12:03 +0000
Message-ID:	<CAJXU7q_8CA33vqqz_sg0NsbgwdFsFW8O-_WMy2NEY9M+Lhnj8A@mail.gmail.com>
Subject:	Re: [geda-user] [pcb] why no clearpoly on silk
To:	gEDA User Mailing List <geda-user AT delorie DOT com>
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

--001a1141068c20ec2f05465d5354
Content-Type: text/plain; charset=UTF-8

On 18 Jan 2017 11:11, "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

Maybe I got something wrong. Normally clearance is between copper while the
silk is painted on both?


You are correct, but there is no technical reason why you can't make lines
on silk cut into (clear against) polygons on silk.

Doing this makes the code and behaviour more consistent, although there is
not the electrical reason for requiring it.

This said, you can't necessarily extend the logic completely to match. For
example, I toyed with connectivity based island removal - that wouldn't
make sense on silk layers.

Thinking about it, whilst you could use the "keep biggest piece" rule with
silk, I'd be tempted to just start with "full polygons" only. (For the
default flags if importing an old board).

Peter

--001a1141068c20ec2f05465d5354
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 18 Jan 2017 11:11, &quot;Nicklas Karlsson (<a href=3D"mailto:n=
icklas DOT karlsson17 AT gmail DOT com">nicklas DOT karlsson17 AT gmail DOT com</a>) [via <a href=
=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>]&quot; &lt;<a h=
ref=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>&gt; wrote:<b=
r type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Maybe I go=
t something wrong. Normally clearance is between copper while the silk is p=
ainted on both?</div></blockquote></div></div></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">You are correct, but there is no technical reason wh=
y you can&#39;t make lines on silk cut into (clear against) polygons on sil=
k.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Doing this makes the =
code and behaviour more consistent, although there is not the electrical re=
ason for requiring it.</div><div dir=3D"auto"><br></div><div dir=3D"auto">T=
his said, you can&#39;t necessarily extend the logic completely to match. F=
or example, I toyed with connectivity based island removal - that wouldn&#3=
9;t make sense on silk layers.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Thinking about it, whilst you could use the &quot;keep biggest piece=
&quot; rule with silk, I&#39;d be tempted to just start with &quot;full pol=
ygons&quot; only. (For the default flags if importing an old board).</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">Peter</div></div>

--001a1141068c20ec2f05465d5354--

- Raw text -