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=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=z3HfquKLFQ1Sp4CuZXZWazauPiYBtZM2AYwIU55j/oU=;
	b=lSVsHlHAAvb2s5BkK7GnVwN8OLwUb0fv7PjcKyzXIl3preA6NEzml6PrvXV13id9OA
	3c14kcOc5o2Jqccj9/NhlyHPzg/qPjRTkUYdKsurGvuKLl6S6N6Lei0LRirHVNKvyYLW
	4l1oPhUvaAk/FIZUuRbBgHxnal4wlyMVrWYwpIqJCP9uT1BHs2S1Jr7hr1EDU+mKCpSj
	Of1iZO14NRun8+OSSSH9CPDmVuckhIbY4YnkVaLHMWEQzPg2HnwsRoMkadAdmwEUyR0k
	E9M6cli5lkJD6jtXkIRbLWWbVfOJRrE2awlhCIwrG82I5l7s19E1Xc8ANR25L7QYavCM
	jwdw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type;
	bh=z3HfquKLFQ1Sp4CuZXZWazauPiYBtZM2AYwIU55j/oU=;
	b=Z5n1fLo15/1Yq0j/L89Mrxc6b3tDd13TSBOJ2z0KWtLO4ouwKODEdHY/LSZVN42o/R
	Hi1M7x05kaoQBhlevNypMEVuAQuXatU7n9ovHLpbN5yAo4cW1GmVabNHFRZaBiP3y8j3
	Vz7MzKy08WI1tonvCA8dBvuS00pdYgL86Z1b27toSmvsItBtGv35iB6szAuXS8kWhrnT
	FRk8TPqL5G3ckV5Pg4KqqVwy5D/G1Y6v4BXXsJTxRUINQRjtowSocH8BkVDZUIdqmaqM
	QhVhBJG7NMPRiheBi/eaczarsFPC6f6y9zbdtKh69/wA6CATpQQ9cbDsUGdKDDpl8QKu
	kJQw==
X-Gm-Message-State:	AG10YOT5AnI8i6TB+5OK+Wywl7VcTZ4ohRtzF5UdrwVG08A3Vpw8CAGvFsQJClbSoUM4bnH+wuzz7hPeKCHujg==
MIME-Version:	1.0
X-Received:	by 10.28.5.203 with SMTP id 194mr7227012wmf.101.1455048210652;
	Tue, 09 Feb 2016 12:03:30 -0800 (PST)
In-Reply-To:	<CAC4O8c9PMWjswXjcO7E9HK31eBVuOSnoOBbLNtYZ7PYTCn-KaQ@mail.gmail.com>
References:	<CAC4O8c-XG7N2Y8YxfrgX-zER5kS9n1Pq+xwi5UMLoS8EpadYRw AT mail DOT gmail DOT com>
	<201602090508 DOT u1958Mv1023697 AT envy DOT delorie DOT com>
	<CAC4O8c8wYq8uFzsY2gMnj4z=msWJA9KJgeTxSR27-2NxjF0Dgw AT mail DOT gmail DOT com>
	<201602090521 DOT u195LYdK025191 AT envy DOT delorie DOT com>
	<CAC4O8c85TCxrDe1WBJkxXQFV-Ob8C5Ow1-q2OoSM5f=7f6DnFg AT mail DOT gmail DOT com>
	<201602090539 DOT u195d6BR026831 AT envy DOT delorie DOT com>
	<CAC4O8c9PMWjswXjcO7E9HK31eBVuOSnoOBbLNtYZ7PYTCn-KaQ AT mail DOT gmail DOT com>
Date:	Tue, 9 Feb 2016 11:03:30 -0900
Message-ID:	<CAC4O8c_d2jqOb=rex4j1aodY_C2Hg=Fbx9mnp_Uacbhmw-mBug@mail.gmail.com>
Subject:	Re: [geda-user] what is 'New polygons are full ones' supposed to do?
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	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

On Tue, Feb 9, 2016 at 10:45 AM, Britton Kerin <britton DOT kerin AT gmail DOT com> wrote:
> On Mon, Feb 8, 2016 at 8:39 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>>
>> IIRC the option is newer than polygons; the default behavior used to
>> be the only behavior.  If you think it should be changed, come up with
>> a good case for it and present it in a launchpad bug report.
>
> So we have Gabriel also saying they have caused him trouble.  The
> polygon interface is overall weird enough to use that I gave up and
> didn't bother for years, and that's what I'd like to fix.
>
> In thinking it over it is a harder call than I though at first, as
> tiny invisible conductive slivers could indeed be quite nasty.  The
> proper place to handle this is the connectivity check or DRC though.
> I'll take a look at how these behave with respect to polygon slivers.

Looks like connectivity tests behave as if full poly is always off:
they don't notice any poly fragment that would be eliminated if the
poly wasn't 'full'.
Given this bug I guess the full poly default can't be changed, but
sheesh that should really be fixed if we're going to advertise full
poly as being available at all.

Britton

- Raw text -