Great! So you're not really using the direct_io branch now, but just standard Espruino? It's a shame - can you see the pins changing state?
The brightness is probably because those rows are left on for slightly longer... I guess en controls if the row is actually lit? If so, just adding arr.push({callback:en.set.bind(en)}); should fix it?
I guess the lack of brightness is because now we're actually able to push the data out quickly - flickering might be because something is stopping scan from getting called when it should be.
My next step will be to create a graphics driver, using Graphics.createCallback to get rid of prep step.
I'd have thought that might be quite slow... On Pixl.js/etc we just have g.flip() that you call when you want to display what you rendered (which is basically what prep() is doing) - or even if you want to avoid that you could check g.getModified() to see if anything has changed?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Great! So you're not really using the direct_io branch now, but just standard Espruino? It's a shame - can you see the pins changing state?
The brightness is probably because those rows are left on for slightly longer... I guess
en
controls if the row is actually lit? If so, just addingarr.push({callback:en.set.bind(en)});
should fix it?I guess the lack of brightness is because now we're actually able to push the data out quickly - flickering might be because something is stopping
scan
from getting called when it should be.I'd have thought that might be quite slow... On Pixl.js/etc we just have
g.flip()
that you call when you want to display what you rendered (which is basically whatprep()
is doing) - or even if you want to avoid that you could checkg.getModified()
to see if anything has changed?