On Apr 11, 2004, at 3:56 PM, harry eaton wrote:
Ahh, ok. The one I'm using is from mid-February. I'm pulling down the current sources now and will give it a shot. Thanks!I have made several improvements to it recently (in the CVS tree, no snapshot yet) including a few bug fixes. It still has some quirks, but works pretty well.
Surprisingly, it'sOk. what I experienced wasn't *incorrect* output in the strictest sense, just that it was pretty messy. (I mean no offense by this...I think your work is excellent)
usually faster and better with fewer layers (it will route on any layer
that's visible). If you have some specific examples of bad output, please
send it my way.
DJ wrote the trace-optimizers in order to "clean up" many things that theYes I noticed that stuff. Is there some reason why those things aren't done automatically during the route, or is that the future plan?
auto-router leaves behind.