#INKSCAPE GCODE TOOLS PLUGIN CODE#

The current code sends strings to the socket, but the socket really, really wants bytes.

A function that stringifies these in some way has changed the way that it behaves, and now the 'M' that is part of the SVG instruction is no longer being treated as part of a string but seems to be treated as a key toвЂ¦ something? It looks like instead of being flattened into a string that the path is being parsed as some sort of key-value pairs.

It looks like there is a part of the code that takes non- path aspects of SVGs, such as rects and converts them to SVG paths (before converting these to GCode).

bytes in the socket connection.ДЄpologies for double-posting (if that is against this communityвЂ™s norms?). In addition to the new methods, there are some changes based on levels of ''quoting'' and with strings vs. Inkscape renamed and reorganized a lot of stuff for Version 1, so some of the older methods needed to be swapped out. On the other hand, the main Python file needs a lot of changes. Once those changes are made, the extension is no longer grayed out, and you can experiment with it. inx file is pretty easy to fix based on the guidelines in the Inkscape wiki about deprecated options.

It does not draw the robot can wave вЂњHello,вЂќ but the extension doesnвЂ™t yet do anything useful with moving the robotвЂ™s arm. It can also communicate minimally with the robot by asking for (and receiving) the version information. However, it is no longer grayed out, which means that it can be debugged via inkexerrormsg(). IвЂ™ve looked at the plug-in, and IвЂ™ve made a small amount of progress towards updating it for Inkscape 1.

Inkscape gcode tools plugin