Hi guys, (I've CC'd Harry, as git blame suggests that he wrote the relevant code - or was the last to run "indent" on it ;)).
I distilled Michael's board into a small test-case.. It looks like the teardrop plugin's use of arbitrary angle arcs has exposed a bug in the the intersection calculation of arcs. (And their bounding boxes look to be wrong as well). I've removed all but the two arcs necessary to trigger the bug. It looks like the bug is a false-positive from find.c's ArcArcIntersect () routine. The arc bounding bounding boxes appear to be wrong - which permits them to be tested against each other, and it appears the bounding box is also used in the intersection calculation, possibly causing further badness. I _hate_ arcs and related geometry.. they caused me no end of grief in gschem, so I'm not feeling keen to dig into the code and debug it myself! Best wishes, Peter C.
arc_short_bug.pcb
Description: application/pcb-layout
_______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
_______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
