These are chat archives for Makuna/NeoPixelBus

16th
Aug 2018
Michael Miller
@Makuna
Aug 16 2018 06:46
Michael Miller
@Makuna
Aug 16 2018 06:59

There is nothing specific in my library for serializing layouts. Its a rare case to need it and it is left up to the developer to implement. Further, the design of library makes dynamic layout types very complex.

For dynamic layout sizes, you will need to load the properties yourself from a file format of your making, and apply them. For width/height/etc is just properties that you load then pass as you construct it dynamically (calling "new") rather than statically (global variable).

For dynamic layout types (like ColumnMajorAlternatingLayout) it is much harder as there is no base class for layouts. You will have to define and use an enum variable that represents all the layouts you want and write the code to constructs and then uses the right one. This gets real ugly quickly.

imKp
@imKp
Aug 16 2018 18:16
Thank you for your suggestions. For the timing let's say we recompile everytime we need to change layout. Dear Michael, say i need to load data frame by frame from a SD card and transfer to my Matrix how many pixels can i control. I have created a js page where I can create
Thank you for your suggestions. For the timing let's say we recompile everytime we need to change layout. Dear Michael, say i need to load data frame by frame from a SD card and transfer to my Matrix how many pixels can i control. I have created a js page where I can create pixel by pixel design and can store color of each pixel. Help me, I'm just not getting where to start.
Michael Miller
@Makuna
Aug 16 2018 20:51
See NeoBitmapFile in Wiki for how to stream an image from a bitmap file to a strip.
The number pixels is all about RAM you have on your Arduino device. My library does have a limit 65536 pixels. Times by three and you have the minimum amount of RAM needed for RGB pixels.