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.
I wanted to make some screenshots of some things I was doing with this graphics package,
so I implemented a way to get SVG output. If you find it interesting, feel free to add it
to the library (or any similar driver libraries you have).
SVG logging sends equivalent SVG directives to the ESP log (usually uart0).
It logs at the logging level and with the logging tag specified. That
should make it straightforward to use text tools to carve the actual SVG
out of the log. There is an optional "cut line" argument to the lcdSvgLoggingEnd.
If provided, it is logged as-is and could be used to automatically separate
multiple chunks from the overall output.
There is no inherent overall background color. If you want one, you
should start with lcdFillScreen() within the SVG logging.
SVG output can be quite verbose (especially for things like text that are
drawn a pixel at a time). It also slows things down a huge amount. In fact,
it makes things so slow that there are task delays of 1 tick sprinkled
throughout to avoid tripping the task watchdog timer.