Wykres commitów

4 Commity (633ec88186106b9a9604f418b5f527d6d8ff888d)

Autor SHA1 Wiadomość Data
Lex Neva 633ec88186
windows build (#79)
Ink/stitch now supports windows!
2018-02-19 21:43:39 -05:00
Lex Neva 4c5e578939 fix repeated colors showing as random 2018-02-17 10:13:09 -05:00
Lex Neva 72d52dc317
framework for translations (#55)
sets up all the plumbing to send strings to CrowdIn for translation and incorporate the results
2018-02-04 22:38:24 -05:00
Lex Neva fabe5bcd32
Fix simulate (#42)
* Simulate now works regardless of the output format you chose when you ran Embroider.
* Simulate (and the preview in Params) now respects TRIMs.
* Inkscape restart required (embroider.inx changed).

This one kind of grew in the telling. #37 was a theoretically simple bug, but in reality, the code necessary to fix it was the straw that broke the camel's back, and I had to do a fair bit of (much needed) code reorganization. Mostly the reorganization was just under the hood, but there was one user-facing change around the Embroider extension's settings window.

Way back in the day, the only way to control things like the stitch length or satin density was through global options specified in the extension settings. We've long since moved to per-object params, but for backward compatibility, ink/stitch defaulted to the command-line arguments.

That means that it was possible to get different stitch results from the same SVG file if you changed the extension's settings. For that reason, I never touched mine. I didn't intend for my users to use those extension-level settings at all, and I've planned to remove those settings for awhile now.

At this point, the extension settings just getting in the way of implementing more features, so I'm getting rid of them and moving the defaults into the parameters system. I've still left things like the output format and the collapse length (although I'm considering moving that one too).
2018-01-28 16:10:37 -05:00