Add stub implementation for local testing#1366
Conversation
|
Do you have a video of this running? |
|
This is a video of demo_simple with some extra delay added (so it doesn't run at 10,000 FPS) And this is a screenshot of an effect I'm tuning with 50x100 strips |
|
Pretty cool, thank you for the video and screenshot. |
|
Hello @sethtroisi. I like this idea very much, could you please share a description of your build environment containing tools, scripts/makefile? Thank you! |
|
I have three versions of my project all sharing the same lights driving code. I target esp32, photon particle, and do tuning in my desktop. I do all the programming in VS Code. VSCode has an extension for the photon particle it simple take all the cpp and h files and passes everything to gcc, compiling everything without any config. For the esp32 I cloned a FastLED demo from espresso which uses cmake. The build tool is ninja(?). Finally and most simple is my new desktop visualizer. I tend to compile the FastLED source files to object files then use Let me know if other details would be useful. |
manually merged in stub from #1366
|
Thanks, merged in manually: |
|
Thanks for merging this. It's so nice to have fewer branches and get to use a clean upstream :) |
|
What's thsi effect called btw? |
I wanted to test some of my patterns on my computer were it's much quicker to compile, test, tune, and iterate.
So I wrote a little wrapper demo_simple.cpp around FastLED so that I could see the pixels on my computer (while still using 99% of my same pattern code).
I'd love to upstream the FastLED Controller Stub if you consider it reasonable. I think I got the right pieces in the right place and I'm happy to change if there are things I've messed up.
FastLED continues to make my art fabulous!
EDIT: Looking at the tests using
defined(__x86_64__)might conflict on some platforms, I'm open to better solutions; possible passing in-DSTUB_IMPLor adding a setting a new#defineto fastled_config.h