The idea presented to use Inkscape (or any vector program that traces, even
Lightburn) to trace out the bitmap is a solid valid approach. The extension
just makes things that much better. I've done this many times and learn a
bit more each time. Unfortunately, I forget more than I remember, so I get
to learn some things over again.
The reference to holes also is a consideration. The extension for Inkscape
creates a separate polygon path for each appropriate segment. One can pop a
into the code to determine which is the major or primary outline, then //
comment it out and comment the line to identify it.
The remaining "islands" can be commented or # identified and pushed into a
difference environment if they are holes.
One thing I've found is the Inkscape extension dumps a scale factor that
isn't accurate/realistic and I change the value of the scale line to 1 to
get the size correct.
If the extension is used, experiment with the "force line output" of the
extension. One aspect of Inkscape trace is that you'll get a path for each
side of the stroke. In one setting, the walls of the OpenSCAD output are
stroke thickness with an empty middle, while the other setting generates a
solid shape. The solid shape method requires the above referenced difference
section if there are holes.
If you decide you don't like the extrusion thickness selected in the
Inkscape extension, that's also a value easily changed in the resulting
code.
You'll find different versions of this extension on Thingiverse. The most
recent has some peculiarities and I've been using "second from the top"
enough to want to avoid changing something that works. I've also read that
the newest version of Inkscape (higher than 0.92) might have complications
when it comes to some extensions. I didn't pursure that avenue either.
--
Sent from: http://forum.openscad.org/
The idea presented to use Inkscape (or any vector program that traces, even
Lightburn) to trace out the bitmap is a solid valid approach. The extension
just makes things that much better. I've done this many times and learn a
bit more each time. Unfortunately, I forget more than I remember, so I get
to learn some things over again.
The reference to holes also is a consideration. The extension for Inkscape
creates a separate polygon path for each appropriate segment. One can pop a
# into the code to determine which is the major or primary outline, then //
comment it out and comment the line to identify it.
The remaining "islands" can be commented or # identified and pushed into a
difference environment if they are holes.
One thing I've found is the Inkscape extension dumps a scale factor that
isn't accurate/realistic and I change the value of the scale line to 1 to
get the size correct.
If the extension is used, experiment with the "force line output" of the
extension. One aspect of Inkscape trace is that you'll get a path for each
side of the stroke. In one setting, the walls of the OpenSCAD output are
stroke thickness with an empty middle, while the other setting generates a
solid shape. The solid shape method requires the above referenced difference
section if there are holes.
If you decide you don't like the extrusion thickness selected in the
Inkscape extension, that's also a value easily changed in the resulting
code.
You'll find different versions of this extension on Thingiverse. The most
recent has some peculiarities and I've been using "second from the top"
enough to want to avoid changing something that works. I've also read that
the newest version of Inkscape (higher than 0.92) might have complications
when it comes to some extensions. I didn't pursure that avenue either.
--
Sent from: http://forum.openscad.org/
