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=mime-version:references:in-reply-to:from:date:message-id:subject:to;
        bh=WWDqTdbZnFuEpuNqQ95v+Dk2N33CCIa2rNAhOcdj+QA=;
        b=P8RpGqMe1GpuLDJwYVcLiv2pSLMIQDFqrdjSEKu4i0Yw/I32Gz6otaU5EtYTkLQOl6
         bpuU3keBdYOgBqVImSjoWCNP45MpxuL3grLzNbsCio+0FzozEqRFry6vge2KmVmaoi1X
         k30c/yz8Av3jTH3o6+NMUMUkv+77nXIoCrAz/DtzosbCkW5CnEK40QMf8fJznqDcGqEP
         SmXlOSmfQEamZBHg7vtosWIcv952N8IlZt9rMoQ61ezTlg6jL6T29Y5GM4EoIzkvBkaC
         zFhwdscoJ15d7FhwzcZ7C33f0cAH/77t5k+Hgp3mxgD/tIih4Oit8FoyX3DYu0uHrHdb
         EeNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=WWDqTdbZnFuEpuNqQ95v+Dk2N33CCIa2rNAhOcdj+QA=;
        b=SMlaowlvSRBbl+T1rGzBUb5Gw545XPONmu83fg1AJ6MYfiq10G/yO5pVVUlAMGBtOn
         ODy2iG9lI0S+0Tsj+hwNZklNEWvn0L11bN+kx/6q65h77nKiwIkDI2BF3FFrFM0voYDH
         Kdvj822IQJhGJGegAiXhtfvpJa3u7/dLqi91tnSp5z5povwD6Aw/UMf8KuEsLj4HfUTR
         MpI54WdRQWjDnIbGiU1IvaRU7+v3NFWRr/F0LyQzqg6chKkFTaSB1o8M+k5eTxzROqKo
         JTFamyx12YWjK5fOjJQP+SaWcP2Q6ZrrUcORANx13KnZp3HXiWPo4S/O8casPz49BOMP
         +bHQ==
X-Gm-Message-State: AGi0PuaH6nssP5XCq8xAjYg74MkHo6M6tE43xKs1WCwXQux57m56jREr
	0VNhEd5TbrQPXgtk4Yzc6E4hioFL1SVEby749EeY7Ico
X-Google-Smtp-Source: APiQypI78F2LcWVy6BfwGcbsJNxwScsgLGaJ7O/awbJhpnFX/x3CB7MKkbFECY45XYJ1ZtddY2EcpxdnZymCfOpTHuA=
X-Received: by 2002:a25:d48e:: with SMTP id m136mr16362752ybf.88.1585944456380;
 Fri, 03 Apr 2020 13:07:36 -0700 (PDT)
MIME-Version: 1.0
References: <CAC4O8c9baAQTW4bqaHLWJ=395oQfqwc6ySO2kAGD3YM5Au-nhg AT mail DOT gmail DOT com>
 <xno8s8qvp4 DOT fsf AT envy DOT delorie DOT com>
In-Reply-To: <xno8s8qvp4.fsf@envy.delorie.com>
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Fri, 3 Apr 2020 12:07:25 -0800
Message-ID: <CAC4O8c9YUVj6+5FUFHx5dDLkLBUjXaz5qs+n3RtTBgngPJ2EdQ@mail.gmail.com>
Subject: Re: [geda-user] Fwd: [pcb-rnd] connectivity bug -> fullpoly again
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset="UTF-8"
Reply-To: geda-user AT delorie DOT com

On Fri, Apr 3, 2020 at 10:57 AM DJ Delorie <dj AT delorie DOT com> wrote:
>
>
> IIRC Peter and I talked about this long ago, and one solution we came up
> with was to have a "polygon stack" so you could do things like "invert
> this section" or "cut this polygon with this line" (different than
> clearing a polygon with a trace).  The user would edit the things at the
> bottom of the stack (the original polygons, cut lines, etc), but the
> system would see the "virtual polygons" at the top (result) of the
> stack.  It added a bunch of functionality and fixed the full poly
> problem, but neither of us ended up implementing it.

This sounds very much like what Igor has just implemented as a fix in pcb-rnd.
It would be good, but as far as I'm concerned it isn't absolutely required.
fullpoly is one of those things in pcb that I only ever used because I didn't
actually know what it did or what the risks were, simply not using it was a
very easy solution.

> So yeah, old problem.  Bug?  Feature?  You decide :-)

I don't understand how this can be construed as a feature.  For all it's
alleged problems over the years, pcb has only actually lied to me twice that I
know of.  First time was by failing to mention actual shorts during DRC, that
has been resolved by a simple warning about the issue in DRC.  This is the
second time.  I would very much like to see it addressed somehow.  If there is
interest (i.e. if it's guaranteed to get merged) I'll try to prepare a small
patch that mentions the issue in the documentation and in DRC (warn if it
sees fullpoly).

Britton