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=o2CJhgFBjV08kPMngM+4k+kj+xn2C4XpRU80DaImyX8=;
        b=iVtzVXg3N1Hl/n92LGh4UmBJeFIlxwEefME7m7kM6xBBE8AhEYtL6LF7wwSH1jwf3L
         MA5eq97W2Sx70hFfXGOXUEhicwtO0zAnG4hudmgRe0b26pumx/Gu9DMj28zX4oNgbvXo
         UvXVKfEXsB9inAGsX/CQgkFXtGYyjJpBisUluAx4POFEFy0K3rZLbGSXe1Z5zVTG6PTt
         kQw2YoErMFR8U5fqJgsd/KnTiHH3k1UvUb1jJ8VcL/aYwZ8ceHia/RN02sspmguzDH1u
         s7CZo+Lo1ypTGfuC/ATgycq9cLloT7cQV/I7ahmcWgvi6Avt/zbMYnE5f0ByQKl1lx8s
         FYzw==
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=o2CJhgFBjV08kPMngM+4k+kj+xn2C4XpRU80DaImyX8=;
        b=OS1a9wgaiT5GwFzwZFuFRg0mpLquJ6YoDmGm5GLlqIyCBk6iOH+3fidUaNTn2tYMBc
         1f9SDH2O5Xj2qSWLs+4Up5OOOf07Cuc37Nsz2bJkhRHnjiVgLfqfeyGNn8iq+VyfjWqg
         23hcdfOLfn/aQGPGx9xO8PCFbposa/h0Gv0H4yXk44joVIUjqFGtibDsiqCDkiBRPIpM
         +nh1pUsnvCVMk2LSoHOkvVQxWHZIvc0EMjfEy3WfWRHWTmJFiLrL0cYg/ZmiHQrrcQl3
         rYPPKQeO2ozCWRP+bVtL1bpzSY/Wi8Z03EpUigx91eHgYjpQkpItTLkZ3538N8qrBKd0
         CuNw==
X-Gm-Message-State: AG10YOQtYbUAgK+FshLFQKNU5KmLNn4gYmlkQkGrakVSUToaqaJrc/yXwP/XihEo2EUcuDnqguS9xAxVIMBUlQ==
MIME-Version: 1.0
X-Received: by 10.194.19.164 with SMTP id g4mr35404382wje.120.1455047117943;
 Tue, 09 Feb 2016 11:45:17 -0800 (PST)
In-Reply-To: <201602090539.u195d6BR026831@envy.delorie.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>
Date: Tue, 9 Feb 2016 10:45:17 -0900
Message-ID: <CAC4O8c9PMWjswXjcO7E9HK31eBVuOSnoOBbLNtYZ7PYTCn-KaQ@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
Content-Type: text/plain; charset=UTF-8
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

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.

Britton