So three ideas for images… @wizard might offer better insight into the possibility and limits of them all:
1: websocket setting of a variable which would be an encoded image. Concerns: size and saving
2: Generating code from Static Patterns
Write a simple image to data converter and paste output into new pattern. Could be combined with #1 to make a “image pattern” maker/pusher.
3: the preview image is really a small jpg
See "Improving" Patterns
And it’s sent to the PB as part of uploading an epe…
If there is a way to access that from within PB code (and If there isn’t, I wonder if @wizard could easily add that? Maybe checkbox to turn off pattern preview regenerator for a edited pattern, too at the same time, so once it’s set that way, it won’t be rebuilt from the pattern itself?), then perhaps a small jpg that contained exactly what the current one does (150 frames of limited pixel data) could be used to populate a POV. Most are short strands, and that jpg is already being stored for every pattern. We’d want a function to pull the data into useful format, line at a time, just like it’s done on the web interface now. This seems like the most promising approach, with some work by Ben required, but making PB much more POV friendly.