| ID: | 4177 |
| From: | Majenko Technologies <ma...@majenko.co.uk> |
| Date: | Fri, 12 Jun 2020 12:55:19 +0100 |
| Subject: | Re: [pcb-rnd] PolyHatch() countour tracing bug |
| in-reply-to: | 4165 from Erich Heinzle <a1...@gmail.com> |
--000000000000f62b5b05a7e1c02a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I just did my first footprint where I used PolyHatch(0,c) on a rectangle to
draw the silk outline. I think that might be my replacement operation for
about 80% of footprints instead of the 45=C2=B0 crosshair.
On Thu, Jun 11, 2020 at 11:50 AM Erich Heinzle <a1039181@gmail.com> wrote:
> I'll be using polyhatch() a bit when I get around to exporting some thing=
s
> for laser cutting +/- cnc routing.
>
> Erich.
>
> On Thu, 11 Jun 2020 18:50 Majenko Technologies, <matt@majenko.co.uk>
> wrote:
>
>> Great. It's not something that would ever affect me directly, but it
>> could cause headaches for people (the one person?) that wants to export =
to
>> protel...
>>
>> On Thu, Jun 11, 2020 at 8:11 AM <gedau@igor2.repo.hu> wrote:
>>
>>>
>>>
>>> On Wed, 10 Jun 2020, Majenko Technologies wrote:
>>>
>>> >Did I not attach it? I could have sworn I did. Oh well, that was silly
>>> of
>>> >me. Here it is.
>>>
>>> Thanks! I've spent some time on debugging this, and came up with the
>>> attached minimal case.
>>>
>>> This is a variant of a known problem in our polygon offseting code: if
>>> there is a sharp corner with a lot of other polygon corners nearby, it
>>> gets confused. Easiest to see on the attachment with {m d t} and
>>> PolyHatch(0,c).
>>>
>>> Such situation most often happens with round cutout touching another
>>> cutout resulting in those pin like, crowded peninsulas. This does not
>>> happen if your polygon is just a plain hand drawn polygon on silk with
>>> no
>>> clearing objects in it (I believe that was your use case).
>>>
>>> I've added this to our long term TODO: this should be handled when we
>>> finally rewrite the poly lib.
>>>
>>> Regards,
>>>
>>> Igor2
>>
>>
>>
>> --
>> *Matt Jenkins*
>> Majenko Technologies
>> https://majenko.co.uk
>>
>
--=20
*Matt Jenkins*
Majenko Technologies
https://majenko.co.uk
--000000000000f62b5b05a7e1c02a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I just did my first footprint where I used PolyHatch(0,c) =
on a rectangle to draw the silk outline. I think that might be my replaceme=
nt operation for about 80% of footprints instead of the 45=C2=B0 crosshair.=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Thu, Jun 11, 2020 at 11:50 AM Erich Heinzle <<a href=3D"mailto:a1=
039181@gmail.com">a1039181@gmail.com</a>> wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">I'll be using pol=
yhatch() a bit when I get around to exporting some things for laser cutting=
+/- cnc routing.<div dir=3D"auto"><br></div><div dir=3D"auto">Erich.</div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Thu, 11 Jun 2020 18:50 Majenko Technologies, <<a href=3D"mailto:matt@=
majenko.co.uk" target=3D"_blank">matt@majenko.co.uk</a>> wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Great. =
It's not something that would ever affect me directly, but it could cau=
se headaches for people (the one person?) that wants to export to protel...=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Thu, Jun 11, 2020 at 8:11 AM <<a href=3D"mailto:gedau@igor2.repo.=
hu" rel=3D"noreferrer" target=3D"_blank">gedau@igor2.repo.hu</a>> wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On Wed, 10 Jun 2020, Majenko Technologies wrote:<br>
<br>
>Did I not attach it? I could have sworn I did. Oh well, that was silly =
of<br>
>me.=C2=A0 Here it is.<br>
<br>
Thanks! I've spent some time on debugging this, and came up with the <b=
r>
attached minimal case. <br>
<br>
This is a variant of a known problem in our polygon offseting code: if <br>
there is a sharp corner with a lot of other polygon corners nearby, it <br>
gets confused. Easiest to see on the attachment with {m d t} and <br>
PolyHatch(0,c). <br>
<br>
Such situation most often happens with round cutout touching another <br>
cutout resulting in those pin like, crowded peninsulas. This does not <br>
happen if your polygon is just a plain hand drawn polygon on silk with no <=
br>
clearing objects in it (I believe that was your use case).<br>
<br>
I've added this to our long term TODO: this should be handled when we <=
br>
finally rewrite the poly lib.<br>
<br>
Regards,<br>
<br>
Igor2</blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr"><div =
dir=3D"ltr"><div><div dir=3D"ltr"><b>Matt Jenkins</b><div>Majenko Technolog=
ies</div><div><a href=3D"https://majenko.co.uk" rel=3D"noreferrer" target=
=3D"_blank">https://majenko.co.uk</a></div></div></div></div></div>
</blockquote></div>
</blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><b>Matt Jenkins</b><=
div>Majenko Technologies</div><div><a href=3D"https://majenko.co.uk" target=
=3D"_blank">https://majenko.co.uk</a></div></div></div></div></div>
--000000000000f62b5b05a7e1c02a--
Reply subtree:
4177 Re: [pcb-rnd] PolyHatch() countour tracing bug from Majenko Technologies <ma...@majenko.co.uk>