add option for logging plotting commands to file #207
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a UI option to the EggBot Inkscape extension to optionally log all commands sent to the EBB into a file.
It depends on additions to plotink (evil-mad/plotink#53).
As the field for the filename is empty by default, logging is disabled by default.
A script ebb_replay_log.py (in the plotink repo) allows for replaying the list of commands to a serial port.
Together with changes to the plotink code, this makes it possible to create a design in Inkscape, save the plotting commands into a command log, and then plot the design again without requiring Inkscape.
This is useful for automated / repeated plotting of the same design.