gfvalvo:
Funny, I've never had any problem with it. Including using it on an interrupt-intensive POV project (more than 10,000 interrupts / second).
weren't you the one that was involved in the thread with the guy and his IR codes ? maybe it was someone else, he had APA102's but using FastLED.delay() messed with his results, changing it to delay() nearly fixed it, but of course not quite.
gfvalvo:
Newbies overwrite arrays all the time. That's what they do. Are you proposing that they be discouraged from using integer and character arrays also?
Not really but a library that does do error checking and the memory allocation is in my opinion preferred over one that in the examples shows how to declare but does not explain about error checking.
Deva_Rishi:
Adafruit_NeoPixel strip[ ledStrips ]; // I only bet this is possible knowing how C++ works, try it with just 2 strips to test. but what about the other arguments to the object ?
Adafruit_NeoPixel strip1 = Adafruit_NeoPixel(15, PIN1, NEO_GRB + NEO_KHZ800);
Adafruit_NeoPixel strip2 = Adafruit_NeoPixel(15, PIN2, NEO_GRB + NEO_KHZ800);
the pin number & the amount of leds don't have a default value.
What I do is initialize them at start up. On Arduino I would keep the values in flash. It is possible to add a constructor to NeoPixel that will initialize an array if one does not already exist. I am not experienced with those libraries.
And BTW, newbies learn to color inside the lines after screwing up a few times. It's called learning and it beats the hell out of quitting.