> I think with most polygon libraries, when you do a union, you can get
> back the coordinates of where the overlap occurs. At that point, you
> should be able to zoom in, or generate an image of the offending location.
>
> Perhaps PCB has some code in it that we can use as a starting point?
The problem isn't the code, it's the semantics. If you bloat
everything and get a complex polygon as your "short", it's hard to
report exactly what's wrong. PCB users often complain that DRC
doesn't give them enough information to actually *fix* the drc
problems.
Now, perhaps with some *more* bloat/intersection operations, you could
get a complex polygon that represents the portion of copper that's too
close to other copper? For example, highlighting a semicircle of a
trace that's too close to a pin, while highlighting a chunk of the pin
that's too close to the trace...
But I think what people want to know is the *actual* distance. That's
what fabs give when they reject a board ("Rule was 5.91; your spacing
4.72, at 1453,6143"). It's hard to do that with the bloat/shrink
method.
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel
