Skip to content
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

Check for Line elements in parseSVG paths #1

Merged
merged 1 commit into from
Jul 25, 2017

Conversation

fdraeger
Copy link

I was wondering if it makes sense to cut a Line into 'steps_per_seg' subsegments.
So I am checking for Line objects in the path and create two coordinate points.
This change significantly reduces the number of G-Code commands sent to the robot.
I came across this as I am working on my Inkscape plugin. But I still have some distance to go.
If you are interested: https://github.com/fdraeger/uArmSwiftPro_InkscapePlugin
Keep up the good work!

I was wondering if it makes sense to cut a line into 'steps_per_seg' subsegments.
This significantly reduces the number of G-Code commands sent to the robot.
I came across this as I am working on my Inkscape plugin. But I still have some distance to go.
If you are interested: https://github.com/fdraeger/uArmSwiftPro_InkscapePlugin 
Keep up the good work!
@OssiLehtinen
Copy link
Owner

Looks good, thanks!

The InkScape-plugin sounds awesome!
The svgpathtools package is rather limited and get's confused with many svgs (the 'svgo'-step seems to make things a bit more easily digestable). InkScape can surely do a much better job in parsing the svgs!

Cheers!

@OssiLehtinen OssiLehtinen merged commit 126b451 into OssiLehtinen:master Jul 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants