I'm travelling right now, but you might like to ping a q= uestion to Bert. I reviwed a patch in this area for him, but as I don't= have Internet on my pc on the move, I can't be 100% sure it fixes this= particular bug.

As for full polys being the default - I'm uncertain. Har= ry screwed this up when he added the polygon algebra... Prior to that polys= with no flags were effectively full, and the introduction of the new code = required adding the full poly flag to recreate the old broken behavior.=C2= =A0 (As you note, the connectivity checking code assumes all pieces are con= nected).

I have a branch which fully implements polygon pour regions = that will operate correctly with connectivity checking for each piece, and = even had experimental support for automatic Island removal (now that did be= have in a moderately surprising way, since no polygon would be left unless = you connected something to it with a thermal, or joined line etc...)

I think implementing full polys with a resurrection of ideas= from my old "pours" branch may be the way to go. I wish we could= turn back time and make the flag "biggest-poly-fragment" so we d= idn't break very very old boards...

Harry was not always as careful as we are currently about no= t breaking things.

I'd be happy to change the default to full polys once th= e connectivity checking works and we have some means for Island removal or = small fragment culling.

There is some code which armed l aimed to remove small fragm= ents, but as implemented it was broken - hence is disabled. For the increme= ntal polygon operations to work correctly, we need all the fragments - no m= atter the size, so they need excluding with a flag or similar, not just del= eting out of existence.

On 9 Feb 2016 20:05, "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <<= a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com> wrote= :

On Tue, Feb 9, 201= 6 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.=C2=A0 If you think it should be changed, com= e 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.=C2=A0 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.<= br> >
> In thinking it over it is a harder call than I though at first, as
> tiny invisible conductive slivers could indeed be quite nasty.=C2=A0 T= he
> 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 slive= rs.

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