Skip to main content

in reply to Devine Lu Linvega

“ The file device is not sandboxed, meaning that it should not be able to read or write outside of the working directory.” I feel like one of those “not”s must be wrong?
in reply to max22-

@maxime_andre !!! I just learned how to write many pixels to the screen at once, I didn't see it in the arduino manual, but this makes it all A LOT faster.
git.sr.ht/~rabbits/uxn-m5/tree…
in reply to Devine Lu Linvega

nice ! btw if you want to have exactly 60 fps, you can use micros() to get the time since boot in microseconds, + delayMicroseconds, and calculate how much time you need to delay
in reply to max22-

@maxime_andre I came across this searching for micros's API, and it spooked me.
forum.arduino.cc/t/why-is-micr…
in reply to Devine Lu Linvega

they are using an arduino nano, maybe that's why it's slower. on the esp32, micros just calls esp_timer_get_time.
"This function is fast and has no locking mechanisms that could potentially introduce delays or conflicts. As a result, it can be useful for fine-grained timing, with the accuracy of 1 μs, in tasks as well as in ISR routines."
docs.espressif.com/projects/es…
in reply to max22-

@maxime_andre oh! J'avais meme regardez du cote de la docs de ESP X) haha, merci pour le lien.

Ca roule super vite en ce moment de toute maniere. Y'a un truc qui reste a comprendre et c'est le truc de l'addresse pendant le screen_flush, y'a moyen de conserver ca et de ne pas avoir a recalculer je pense.

in reply to max22-

@maxime_andre M5.Lcd.pushColors(row, w, true); le true permet de garder l'addresse en memoire mais en fin de compte j'avais mal compris la docs.

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.