- Notifications
You must be signed in to change notification settings - Fork13.3k
delay / esp_delay: transparently manage recurrent scheduled functions#8802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
…esp8266#8802)Recurrent scheduled functions will always be running in background.esp_delay()'s interval (intvl_ms) is internally kept to its highest value allowing to honor recurrent scheduled functions requirements.It transparently allows to keep with the arduino and nonos-sdk trivial programming way and still use background services or drivers running regularly.
Recurrent scheduled functions will always be running in background.
esp_delay()'s interval (intvl_ms) is internally kept to its highest value allowing to honor recurrent scheduled functions requirements.This allows examples like
EthClientto keep answering topingwhile "trapped" in adelay().More generally it transparently allows to keep with the arduino and nonos-sdk trivial programming way and still use background services or drivers running regularly.