-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filling zones #11
Comments
set-soft
added a commit
to INTI-CMNB/KiBot
that referenced
this issue
Jun 14, 2020
Implemented in a different way. For all internal commands now we use Python bindings to fill the zones as suggested by @arikrupnik in johnbeard#11 For 'print_pcb' now we ask KiCad to do it before printing (needs v1.4.1)
Very good idea @arikrupnik I was using a weaker strategy in my fork: |
rdeterre
pushed a commit
to rdeterre/kiplot
that referenced
this issue
Nov 9, 2020
README: Make navigation more easy
rdeterre
pushed a commit
to rdeterre/kiplot
that referenced
this issue
Nov 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@johnbeard , thank you for writing this extremely useful piece of software, and for wading through the spartan documentation on the Python API. Your code is the best documentation I've found for many aspects of the API!
One issue in particular has been a stumbling block for me: filling copper pour zones. Going by this comment in your code, it has been an issue for you, too.
kiplot/src/kiplot/kiplot.py
Line 65 in f1c85db
Seth Hillbrand over at the KiCAD forum has been able to answer my question, and I imagine you might find his answer relevant:
https://forum.kicad.info/t/filling-zones-copper-pours-inside-the-python-api/19814
In my own code, I have it as a single line:
If you still want to check whether zones are filled (instead of unconditionally filling them as I do), you can use something like this:
The text was updated successfully, but these errors were encountered: