kicad-developers team mailing list archive
Mailing list archive
Re: Footprint features - stable vs nightly
This doesn't directly address your question - but couldn't the automated
library checker actually load the footprints into KiCad, via the Python
API, to truly verify that they parse in KiCad proper?
On Sat, Mar 11, 2017 at 10:39:37AM +1100, Oliver Walters wrote:
> Hi all,
> Can someone tell me a complete list of the differences between footprint
> "features" in nightly and stable? There is a recent issue where someone
> added a footprint using roundrect pads and broke a library for someone
> using stable.
> I can easily add a search for "roundrect" to the automated library checker
> but what else should I be looking for?
> As an aside, I think it would be **very** helpful if the footprint library
> loader was able to skip over "bad" footprints and continue to load.
> Currently a single bad footprint prevents any subsequent footprints from
> loading. If we had the ability to skip bad ones, then we could add "future"
> footprints and these would simply be ignored by stable version.