How or why?

You should give some information about how/why it increases the speed of the project. :)
Magnie (talk | contribs) 14:21, 19 April 2012 (UTC)
Sure, good idea!
Hardmath123 (talk | contribs) 07:40, 21 April 2012 (UTC)

Run w/o screen refresh custom blocks

Run without screen refresh custom blocks exist in Scratch 2.0; and they do the same thing but with less effort for the programmer. Do you think they should be mentioned in the article?
Jokebookservice1 (talk | contribs) 18:56, 9 December 2016 (UTC)

Additional information on screen refresh

(To the best of my understanding, and somewhat inferred from my knowledge of the workings of the canvas API,) the screen refresh is an essential part of Scratch. It displays changes to the viewport. Any changes made to the graphical content, such as with the pen or by moving or updating the costume or visibility of a sprite are not rendered to the viewport until a screen refresh. By default, Scratch refreshes the screen once every 'frame', i.e. once all blocks have been executed and loops have finished one iteration. This causes a natural delay after every frame. However, one can delay a screen refresh until the execution of a loop is finished by using an atomic procedure, although Scratch forces a screen refresh if the loop hasn't finished in 5 seconds (I believe). This is why putting loops which do not exit or slow loops can appear to cause more lag than is actually occurring -- Scratch is only refreshing the screen every 5 seconds. I believe this information, or an equivalently useful substantial portion of it, should be included.
Ipaddude (talk | contribs) 16:05, 9 June 2021 (UTC)

Cookies help us deliver our services. By using our services, you agree to our use of cookies.