kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #37689
Re: Handling SEGZONEs
-
To:
Seth Hillbrand <seth@xxxxxxxxxxxxx>
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxx>
-
Date:
Fri, 28 Sep 2018 07:59:50 -0400
-
Autocrypt:
addr=stambaughw@xxxxxxxxx; prefer-encrypt=mutual; keydata= mQGiBEM0hxQRBAC2fNh3YOVLu1d5GZ0SbrTNldGiGnCJPLqzEnqFX9v6jmf33TMt6EmSLkl6 Wtfkoj0nVwKxcYmJkA8DX0QAokBkwNIzhSsBzQvthBLIk/5LnPVVKrEXOcL4mUyH1doKlkaE slgJozNa6Av+oavcvD02o1zJOloBbaHlNlyRt7fKswCgtIFlVjWggVH/15KfWk+Qo5JVPbME AIUBAQyL2OAx0n60AWec2WHnO9buHuG0ibtICgUMkE+2MRmYyKwYRdyVwGoIUemFuOyHp0AJ InX4T+vy2E7vkwODqjtMLfIoRkokW74Fi4nrvjlhOAw/vdq/twLbAmR9MOfPTpR4y7kQy1O2 /n+RkkRvh26vTzfbQmrH7cBJhk6aA/9Uwvu3E4zNJgHVZeS0HyWtmR1eOPPRbnkPgJTToX5O KMKzTJI/FX6kT7cFoCamitHrW3BJP4Dx+cMMsa47EGxqVTdbVJ4LjogsXTXxb+0Fn1u4zBdx x3Cer6O7+hqWy7zvpzeC6nSREjqDKa5CgHtv/GLm5uFPOmsjAsnHj2tlBrQmV2F5bmUgU3Rh bWJhdWdoIDxzdGFtYmF1Z2h3QGdtYWlsLmNvbT6IeAQTEQIAOBYhBOffs6CbblRzBkv33BtR cWlZ+CReBQJbFBS2AhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEBtRcWlZ+CReMI8A nRbrLkzp7+c2f0vX7sfg4ICX8LAKAJ9uClo4uJajmZa5zZrL2nKdZlUwIrkCDQRDNIcxEAgA gCru+3/aOC6RCjpvYC72wY+d5SmHphC6yeiV2/mOumyt5MLo/Ps2GznZr11JspqFk5K/Zpvp MMLqqjDZ39+50a2iKRQFJ6NlK+hJWMmj6eJygQrCwYo3Gjc6CqfrqUv+8VSnf/i5sIZmtOVA 4ZjML18MuBvMSsNdVLFJd5HNnYb1iOECpvqdPVh/21LLCEw7MUUGGnHBhCrmk2aJe5hFmcSN g4ldBcXrgMQBwf7aMVoobXBMFDb/IENByXn0llB7Gr2IFMRmNS9/p8s/II1Yl2bTqyX4FSz8 cfn7C9KEz7faZ7wzAcpwHFC/zs3JoAjJ0IEKdNUpIwAlKMzT3CzctwADBQf/cxpG28MKyrqk nNmq/8LQLy+x6FSYXBLjxQz9BiBNYeesDZQ6J5UbL1mjpJzMa5tLZypPYo4bbGyR22hrbyDF K7m6AcVaMIJKl98g4ukMutFfAJyRDaREH5Zl/X1P4u1Z/yaAIy9mKaNbaK1/5djNJ5wCTFen TUgAp9xdc30kGkFDdLJFp5uxDY4P0vaZiZdjUCvDM3Zjv5IzpNOfxVqTUBQNUP/BnnKhkk0p DTD6s3X8S+D0rOtEBQ8K0cwERI/E8EFa8nj0TNw4e2MYGR8wg+SxqJ7z5f0zPY0bO6G9DDFB wYCqzzPWGqdAh9vA5971TAbPERtdFybhkurozp2SfYhJBBgRAgAJBQJDNIcxAhsMAAoJEBtR cWlZ+CResHUAniULLCWiT26ieRTl7N2vS6vBo/DuAJ4m7Ss/gyiW6ybTn1ctDXAUgm2QVQ==
-
Cc:
KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CALHbTmZvonrtsEKt7YZCGbjBQeyhYPQuYZsM1qa7xrk8YYNdHw@mail.gmail.com>
-
Openpgp:
preference=signencrypt
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
Seth,
On 09/27/2018 04:37 PM, Seth Hillbrand wrote:
>
>
> Am Mi., 26. Sep. 2018 um 12:23 Uhr schrieb Wayne Stambaugh
> <stambaughw@xxxxxxxxx <mailto:stambaughw@xxxxxxxxx>>:
>
> On 9/26/2018 3:16 PM, Seth Hillbrand wrote:
> > Hi Wayne-
> >
> > That will be more luck of the draw in your memory management.
> > connectivity_algo.h:643 gets the filled polygon list, which in the
> case
> > of SEGZONE is undefined.
> >
> > -Seth
>
> Why would a polygon list be created for a SEGZONE object? JP, do you
> have any thoughts on this? As ugly as the old segment filling is, I
> would prefer that we maintain accuracy. If the user wants to delete the
> segments and go with a polygon filled zone, that should be left up to
> the user.
>
>
> Ping, JP.
>
> Wayne- We should not be creating a polygon list for the SEGZONE. This
> is the root of the issue. If we convert to plain segments, the board
> looks the same and there is no error. I found a legacy command that
> clears the segments from a SEGZONE specifically. This command does not
> exist in GAL.
>
> I suppose the question comes down to how much legacy handling to we want
> to keep around. Since users cannot create SEGZONEs, it may not make
> sense to maintain the objects and their associated handling complexity.
> Convert to segment gives us a clean break there.
>
> If we do want to maintain the actual SEGZONE object on the board, we
> should port the command to clear it over to GAL as well.
This would be my preference as it keeps with our stance about not
silently changing boards at load time. I think in this case that users
would convert over to polygon fills but I don't think we should force
that on them. I'm OK with not allowing editing of the old SEGZONE
objects since we no longer support them and asking the user if they want
to convert them to a polygon filled zone but silently doing this is dubious.
>
> -Seth
Follow ups
References