.lengthAPI - thanks @rupl
pixel.off()behaviour actually work properly as a result of test coverage - YAY Tests!
stripLengththrows an error
lengthAPI and removal of deprecration notices as a result of this change. Thanks @The-Alchemist
Stripsare now relatively dumb and just operate on the array they are passed which is ripe for further consolidation down the line. ( = more memory for pixels - YAY!)
strip.stripLength()and move to
strip.lengthas the more logic alternative. 0.8 generates warning, 0.9 will throw error, 0.10 will have function removed
stripobject so you can manipulate it from a repl environment
Thanks to @stevemao for the following:
Strip.off()behaviour intuitive so it latches as soon as it's set and turns the strip off.
strip.off()functionality and tests - thanks again @noopkat
set_off()in order to rapidly and efficiently wipe an entire strip of values back to zero in the firmware.