delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] Fwd: [pcb-rnd] connectivity bug -> fullpoly again |
In-Reply-To: | <CAC4O8c9baAQTW4bqaHLWJ=395oQfqwc6ySO2kAGD3YM5Au-nhg@mail.gmail.com> (geda-user@delorie.com) |
Date: | Fri, 03 Apr 2020 14:18:47 -0400 |
Message-ID: | <xno8s8qvp4.fsf@envy.delorie.com> |
MIME-Version: | 1.0 |
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 |
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. So yeah, old problem. Bug? Feature? You decide :-)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |