> Your arc based teardrops are great-looking. Are they hard to
> specify?
Well, there's a quadratic equation and some linear algebra, but
nothing complex compared to, say, DRC or the optimizer. I'm sure
there are corner cases to deal with, though, like via/line ratios too
near 1 to be useful, or so high that the arcs don't generate a filled
teardrop (i.e. relatively thin traces).
> Perhaps instead of these being as you draw things, we could make a user
> scriptable autorouter control do them as a post route process.
A dynamically loadable hid, you mean? Gee, how convenient that we
just added that functionality :-)
> The arc ones especially would stay out of the way of other vias and traces
> already existing.
Usually, although you can't guarantee it. Consider this example,
which shows both "arcs getting in the way" and "non-solid teardrops".
PCB["" 28000 25000]
Grid[1000.000000 0 0 1]
Cursor[0 0 0.000000]
Thermal[0.500000]
DRC[1000 1000 1000 1000 1500 1000]
Flags(0x0000000000001c40)
Groups("1,c:2,s:3:4:5:6:7:8")
Styles["Signal,1000,3600,2000,1000:Power,2500,6000,3500,1000:Fat,1000,10000,3000,1000:Skinny,600,2402,1181,600"]
Via[22000 13000 10000 2000 0 3000 "" ""]
Layer(1 "component")
(
Line[22000 13000 1000 13000 1000 2000 "clearline"]
Line[1000 11000 16000 11000 1000 2000 "clearline"]
Line[16000 11000 16000 5000 1000 2000 "clearline"]
Arc[11000 24000 11000 11000 1000 2000 -90 -45 "clearline"]
Arc[11000 2000 11000 11000 1000 2000 90 45 "clearline"]
)
Layer(2 "solder")
(
)
Layer(3 "silk")
(
)
Layer(4 "silk")
(
)
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
