summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-01-06Use sys.stderr_backup in both save and restorecclauss
There is no __sys.stderr_backup__ defined in the [Python sys] module. __save_stderr()__ adds a variable by that name which is a bit unconventional but it does work. This PR changes __restore_stderr()__ to read that data from the same variable. Without this change, __restore_stderr()__ will probably raise a NameError at runtime because __stderr_backup__ is an undefined name. flake8 testing of https://github.com/lexelby/inkstitch on Python 2.7.14 $ __flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics__ ``` ./embroider_params.py:748:18: F821 undefined name 'stderr_backup' sys.stderr = stderr_backup ^ ```
2018-01-06don't intify floating point coordinatesLex Neva
2018-01-06add scale parameter in simulateLex Neva
2018-01-05add notes about the switch to 96dpiLex Neva
2018-01-04remove pixels_per_mm optionLex Neva
2018-01-04use PIXELS_PER_MM in simulateLex Neva
2018-01-04simulate bugfixLex Neva
2018-01-04parse and use viewBox attributeLex Neva
The viewBox effectively adds global scaling and translation to all shapes in the SVG. Borrowing from inkscape-silhouette, we construct a transform from the viewBox and apply it to all objects. When adding the stitch plan into the SVG, we need to compensate for this implied transformation, which we do by adding its inverse as a transform on the stitch plan polylines. All of this allows us to do away with the nonstandard 10 pixels per mm that was previously hardcoded into inkstitch. Old designs can add a viewBox to switch from 10 pixels per mm to the standard 96 ppi that Inkscape uses.
2018-01-03remove outdated index.htmlLex Neva
2018-01-03more README fixupsLex Neva
2018-01-03Create CNAMELex Neva
2018-01-03Set theme jekyll-theme-minimalLex Neva
2018-01-03readme fixupsLex Neva
2018-01-03rename to ink/stitchLex Neva
2018-01-01add link to video of live preview featureLex Neva
2018-01-01remove live simulation from TODOLex Neva
2018-01-01Merge pull request #10 from lexelby/live-simulateLex Neva
live stitching preview in the Params extension
2018-01-01adjust colors in the simulator to make them visibleLex Neva
Colors too close to white are darkened just a bit to make them stand out against the white background.
2018-01-01add restart option for simulatorLex Neva
2018-01-01render objects in the correct orderLex Neva
2017-12-31make debugging slightly easier by popping up tracebackLex Neva
2017-12-31trim unnecessary whitespaceLex Neva
2017-12-31don't start outdated simulationLex Neva
2017-12-31adjust default simulation speed to always take ~5 secondsLex Neva
2017-12-31show simulate window at startLex Neva
2017-12-31don't mirror Y axis for patchesLex Neva
2017-12-30cancel should not output the SVGLex Neva
also sped up simulation
2017-12-30get rid of thread killingLex Neva
Switching to a cooperative model. This has the downside that a long patch computation will cause the simulate window to take longer to update, but in practice the longest this will be is a couple of seconds (for a very complicated autofill region).
2017-12-30render in a background threadLex Neva
The problem with this approach is that sometimes the SystemExit happens down inside shapely and it complains bitterly (on stderr). May have to rethink.
2017-12-30params simulate windowLex Neva
when you change params, a simulate window opens to preview the results right away
2017-12-28fix trailing whitespaceLex Neva
2017-12-28generalize EmbroiderySimulatorLex Neva
* add ability to use patches instead of a stitch file * add stop() and load() methods to use a new stitch file / patches list
2017-12-28rename draw_one_stitch to be more accurateLex Neva
2017-12-28Merge pull request #8 from lexelby/fix-macosLex Neva
remove uses of `wx.CB_SORT` to fix OS X
2017-12-27remove uses of wx.CB_SORTLex Neva
Apparently that option is not available on OS X. It's easy enough to just sort the values before giving them to wxGTK.
2017-12-24add some new ideas to TODOLex Neva
2017-12-07Merge branch 'master' of github.com:lexelby/inkscape-embroideryLex Neva
2017-12-06add link to youtube tutorial videoLex Neva
2017-12-03Merge pull request #5 from Moini/patch-1Lex Neva
Add update/install script for Ubuntu
2017-12-03Do not install dependencies needed for building wxpython, Moini
... and make sure pip can pick up the package installed via apt.
2017-12-03Install wxpython via apt in Ubuntu autoinstall scriptMoini
2017-12-03Update README for installing wxpython via aptMoini
2017-11-26fix installation script for Ubuntu 16.04, add script to install ↵Moini
libembroidery-convert, adapt README
2017-11-25don't infinitely loop in build_graph heuristicLex Neva
2017-11-23don't omit jump stitchesLex Neva
2017-11-22Move Ubuntu install script, change message to user, update README accordingly.Moini
2017-11-21fix image width in READMELex Neva
2017-11-22add soulstorm brew patchLex Neva
2017-11-20fix param definition for zigzag underlay insetLex Neva
clearly I've never set this manually
2017-11-19switch stitch view from paths to polylinesLex Neva
Polylines in SVG are essentially the same thing as paths, but with no curves. But inkscape-embroidery treats polylines as literal stitches; it does not do satins, fills, etc but instead takes the coordinates and uses them directly as stitches. The advantage in this case is that one can re-run the extension on its own output and get back the same stitch output. Why would you want to do this? Consider the case where you have a basic embroidery machine that can only do a 4x4" square. If you have something that's a bit bigger than 4 inches wide, it might still fit in the square if you turn it at an angle. But working with your entire design rotated at an angle is a total pain, and you'd also have to rotate the angles of all the fills to compensate. Instead, just run the extension, rotate the stitches to fit, and re-run, and your stitch file will work on your 4x4" machine.