Updated KiPadCheck GUI to use a separate file generated from wxformbuilder.
Please let me know how this affects running on MacOS and Linux. Better?
THIS IS FOR NIGHTLY ONLY, NOT 4.0.6 STABLE.
The distribution is now two files kipadcheck.py and kipadcheck_gui.py. Both must be placed in the plugins directory.
The README.md is updated as well to be a bit more organized with ABOUT and USE closer to the top.
Feedback welcome!
This works now on nightly / MacOS, incl Pad/Stencil/Drill and Silk with lots of output in the main project window.
I now need to work out some reasonable values now to test properly. What should I be expecting to see in Eco2?
Excellent! Glad it works!
Eco2 is written to if either Draw All Outlines is selected or if Outline Thickness is non-zero.
(in all fields, blank and non-valid data are interpreted as zero).
If Outline Thickness is non-zero, then pad outlines and text strokes are drawn that are being checked. The silk to pad check first determines if the text box is close to the pad. If so, then each individual stroke is checked. Those strokes are drawn on the debug layer (currently hardcoded to Eco2) if Outline Thickness is non-zero.
If Draw All Outlines is selected, then the Silk check draws all pad outlines and all text strokes on the debug layer.
Incidently, selecting Slow Check will check against text strokes, while unselected will only check text boxes.
Text strokes, in case it isn’t clear, are the individual line segments that, combined, create the letters.
I hope this helps!
Can confirm it works on linux as well 
Thanks!
Coming soon in the next release, fixing something I’ve been annoyed by when entering values for DRC: the lack of changeable units. Why do I have to break out a calculator if the manufacturer gives me different units than what the text box uses?
Note the Text minimum Height value. The default value (if no units are specified) is in mm:
But you can enter the value with any of the available recognized units (the list is large).
When you enter the value, it changes the default units for that entry:
The full value and units is retained in the text box for cut and pasting to other boxes, if you need it.
KiPadCheck GitHub for nightly 406 has been updated.
You can now select min/max drill size (which are measured against the drill set),
select the drill set from a few different metric and imperial choices,
modify units just by entering them in the boxes,
and modify the debug layer (where object outlines are written if you select debug mode).
Data entry overall is pretty tedious because you have to enter everything by hand every time you open the dialog for the first time in a session. I’ll be adding load/save to a file soon.
This is a screenshot of KiPadCheck on the latest Nightly on Ubuntu16.04, I had to toggle View F9-F11 to get the highlight.
Thank you for reporting!!
The toggle view requirement is noted in the main KiCad console window output. I don’t yet know how to fix this. The failing objects have SetSelected() being called on them, but I’m not sure what else is required to get the objects to show themselves as selected when in OpenGL view.
