Why were so many jump stitches used for the back stitches when I chose a thickness of 1 thread (or 3 threads)?
When an even number of threads are specified for the thickness of a back (or straight) stitch, the program generates machine stitches which result in a back stitch getting stitched from one end to the other end, and then back to the starting end. While stitching a particular back stitch, if another back stitch is reached which branches off of the current stitch, the program generates stitches for that branching back stitch. The stitches generated for the branching stitch will complete back at the original stitch which will then be continued. In the case of an odd number of threads per machine stitch, the needle does not end where it starts for a particular back stitch. Therefore, it is not possible to handle back stitches that branch off of a back stitch without using jump stitches. It is recommend that odd values only be used in special cases where you need the full range of thicknesses.
Related Questions
- What option can be specified as an argument to the jdk to increase the thread heap size used by the JDK in the context of the webserver?
- Why were so many jump stitches used for the back stitches when I chose a thickness of 1 thread (or 3 threads)?
- Can I-drain be used in combination with every kind of tile and more precise every tile thickness?
