-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
kikit panelize fails on edge cut in footprint: Board rotation has to be passed as EDA_ANGLE, not a number #663
Comments
I think this is fixed in the upstream version (49363ea). Could you try it? |
Still failing:
|
Unfortunately, I struggle to reproduce the issue on Linux. And I don't own a Mac. I assume this might be related to the numerous warnings from the SWIG wrapper in KiCAD API. I will try to find a way of reproducing it, however, it might take a while. |
I'd love to use kikit on Linux, but Kicad 8 botched Python's packaging and installing the nightly version didn't help. |
If you are on Debian-based distribution, the packaging is already fixed in testing builds of v8 (this how we use it for CI): KiKit/.github/actions/setup-kicad/setup.sh Lines 53 to 65 in 495e55c
|
Yeah I tried that, for some reason I'm not getting the As a matter of fact, I do have the file at I'm not sure how kikit is supposed to be installed as simply doing |
|
|
Ah, you mean this change in recent pip. Due to the way KiCAD handles Python plugins, the recommended way is I have plans for other installation methods, but it is laborious to get working properly (as it has to work on Linux, Flatpak, Windows, and mac), which makes it annoying to test properly. |
That does work but I hope you'll figure this part out in the future! Also, I'm not getting the crashes on Linux so your suspicion that it's Mac related seem correct. |
Prerequisites
KiKit version
python -m kikit.ui, version 1.5.0
KiCAD version
8.0
Operating system
Mac
Description
kikit seems to have an issue when it sees an edge cut inside of a footprint. I went over #189 but it seems there's something different here.
To simplify things I used one of the example commands and I've dumbed down my PCB to just the faulty footprint (an LED) surrounded by a rectangle:
Thank you for this great piece of software.
Steps to Reproduce
See example file at https://gist.github.com/idank/4b257632136e5c33a13bcc4352e76e5b.
The text was updated successfully, but these errors were encountered: