You are reading a single comment by @Robin and its replies. Click here to read the full conversation.
  • Sun 2019.06.23

    Agree with your last sentence @allObjects re Blockly. I also like your idea of scheduleOnce() but would/will the resultant code and understanding be any better than setTimeout()?



    For @Unreality,

    'Is there a max execution time that forced the nodeMCU to reset?'

    Found a nice article explaining both the Hw and Sw resets for ESP8266

    https://techtutorialsx.com/2017/01/21/es­p8266-watchdog-functions/


    EDIT: Sun 2019.06.23
    I like the concept of Blockly, especially for children and individuals (
    yes, there are those that don't get ;-) us!)
    that just don't grasp the concept of programming. From what @Unreality #3 points out, there is a need to have an easier way of explaining in code what is actually going on for each of the 'blocks' involved. A fundamental issue is that the minds concept of 'wait' is much different that how a microprocessor functions, and how code is executed, especially when instructions are interpreted line by line. As both @allObjects and I discovered, using Blockly as a solution is a bit cumbersome, and for us, typing text is easier on the mind.

About

Avatar for Robin @Robin started