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

Lock-Stitch Tie-Off/Tie-On methods and contingencies. #64

Open
tatarize opened this issue Aug 3, 2018 · 0 comments
Open

Lock-Stitch Tie-Off/Tie-On methods and contingencies. #64

tatarize opened this issue Aug 3, 2018 · 0 comments

Comments

@tatarize
Copy link
Contributor

tatarize commented Aug 3, 2018

The current chosen method is to stitch within the adjacent stitch at .33, .66, .33, 0 through that stitch.

There are other methods that might be preferred.

  • Split stitch. Make sure the first stitch is small by subdividing it into small stitches.
  • Small triangle. Create a small triangle stitch at the end or beginning.
  • Divide the first stitch in two and perform a triple stitch (bean stitch). Similar to current.

Contingencies to be considered:

  • First stitch is smaller that 0.5 mm. (Length of 5)
    • Currently if you started with a stitch of length 0. Tie-On/Off would create 5 stitches of length 0.
  • Tie off non-trimmed long-jump
    • There's sometimes need to perform a really long jump operation, and sometimes these jump operations could be tied-off. Though it might be proper to just tell pyembroidery to Tie_Off in that case overtly, rather than have it looking around for such events. Or perhaps utilize the STITCH_BREAK command there.

In theory a properly streamlined version of this would replace the Tie-On Tie-Off settings with their mode and just add a mode for "do nothing". Such things would be breaking changes. And thus left for 1.3.x

lexelby pushed a commit that referenced this issue Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant