I'm noting a number of inconsistencies when writing patterns to an (admittedly ancient) blink1:
Patterns, e.g. a color, time, index triplet - #ffffff,9.00, 0, are taken in order presented, without regard to specified index.
No matter how many triplets are presented, only 12 are inserted, although 32 are reported.
If more than 12 triplets are pushed, the first triplet is skipped and the last is used as line 0.
Time values reported inconsistently: If I write 1.00 (s) it will be written as 1000 (ms?), but in readpattern will show 500, which is what will be played
Color values reported inconsistently: if I write, e.g. #ff5f00,1.98, 4, I will see writing line 4: ff,5f,00 : 1980 : 4, readpattern will yield #ff1c00,0.99,4,. I don't have a good sense as to how accurate this color is.
I recognize that my hardware may be too ancient to deal with, and I'm comfortable with the workarounds I've found, but thought I'd mention these.
I'm noting a number of inconsistencies when writing patterns to an (admittedly ancient) blink1:
#ffffff,9.00, 0
, are taken in order presented, without regard to specified index.#ff5f00,1.98, 4
, I will seewriting line 4: ff,5f,00 : 1980 : 4
, readpattern will yield#ff1c00,0.99,4,
. I don't have a good sense as to how accurate this color is.I recognize that my hardware may be too ancient to deal with, and I'm comfortable with the workarounds I've found, but thought I'd mention these.