As an Allegro user, There are two-letter violation DRC error types which give you an idea about the kind of violation. 'P-P' for pin-to-pin violation, 'P-S' for a pin-to-shape (shape = zone), 'D-S' for drill-to-shape, 'K-V' for keepout-to-via, etc. One can then drill down into the details of the violation to find exactly the elements involved, and the exact constraint being violated.
I think this is just what you're suggesting, Ian and Jon, and I like it too. Fewer buckets of error types to keep track of. Having edge-to-copper clearance separate is nice, I agree. It might also make sense to partition any type of DFx DRC error from a true electrical DRC error since in my mind the path to resolution is different. But in v6 maybe the type of violation won't be that granular to separate electrical and DFx rules? I also think it would be nice to somehow provide a link that will take the user to the area of the UI where the violated constraint can be seen and configured. It can get tricky sometimes to figure out where a constraint is coming from and it's always annoying to feel like I've wasted time hunting and poking around when the tool obviously knows exactly which rule is involved in the error. On Thu, Jun 11, 2020 at 1:49 PM Jeff Young <j...@rokeby.ie> wrote: > It’ll work; there are just more special cases than there are non-special > cases. I felt it reduced the SNR, but I’m not against someone else giving > it a go. > > Are you doing it with the priority system we worked out? > > > On 11 Jun 2020, at 21:43, Tomasz Wlostowski <tomasz.wlostow...@cern.ch> > wrote: > > > > On 11/06/2020 22:27, Jeff Young wrote: > >> I had also originally planned on “compiling” the classic system into > behind-the-scenes rules, but I don’t think that’s going to work out. It’s > pretty easy to agree on priority of all the edge case (pad override, > footprint overrides, netclasses vs. board settings, etc.), but there’s > nothing uniform about them. > > > > Hi Jeff, > > > > I'm actually coding it right now... Why do you think it will not work? > > > > Tom > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
