-
Notifications
You must be signed in to change notification settings - Fork 79
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
What you telling me? #118
Comments
@Pipstapee is it possible to share your .svg file may be something on that itself is causing this. |
I'm going to try a few things. I've used the Extension many times before. |
This is JPEG file. I can not open this in my inkscape. Are this round "Holes". If you can share your .svg then I can try to export on my inkscape and see if any layer or anything else is creating problem or not. |
Here is my flow. Please find attached inkscape and exported file |
Done that buddy, hence me being here. |
Rings.zip |
"This is JPEG file. I can not open this in my inkscape." |
I see you're using ver, 0.2.18.6 what version of Inkscape are you using? |
I am using 1.0 |
So you couldn't possible direct me to a solution because we're both using different versions. |
Inkscape 1.0.2 svg2 shen 0.2.18.7 |
Simple...What you telling me?
Traceback (most recent call last):
File "export.py", line 750, in
_main()
File "export.py", line 746, in _main
e.run()
File "C:\Users\Phil\AppData\Roaming\inkscape\extensions\inkex\base.py", line 140, in run
self.save_raw(self.effect())
File "export.py", line 323, in effect
self.processExportLayer()
File "export.py", line 468, in processExportLayer
kicad_edgecut_string = self.exportEdgeCut(kicad_mod = options.filetype == "kicad_module")
File "export.py", line 659, in exportEdgeCut
y = (path[1][1])
IndexError: list index out of range
Run the extension many times in Inkscape but now it's telling me the above.....What you telling me?
I'm not a coder so keep it simple. I only use Inkscape for one job and that's because there isn't a SVG2shenzhen for Photoshop.
The text was updated successfully, but these errors were encountered: