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)
Needs Work
 Unresolved (see all...)
|
|---|
I asked a group of Scratchers (associated with this studio but not necessarily members) about their knowledge of this topic. 9 answered no, 2 answered "heard of it", and 2 know what it is. This is low. To quote SpinningCube,
[The wiki article] makes sense but it does need a change of terminology
It seems like a lot of people haven't really well formalized their understanding of the script yielding system Scratch has so a lot of people call it what it is not and arrive at false conclusions that explain what they see
The action shown in the article is called loop unrolling, although usually discussed in contexts that don't have artificial loop delays.
This article needs to be rewritten at least and probably moved away from the term "single frame". There currently isn't an article on the virtual machine or sequencer and one probably should be created to link together subjects like this one, turbo mode, frame rate, and run without screen refresh.
Awesome-llama (talk | contribs) 15:24, 9 April 2026 (UTC)
I updated the article. I realized a few things. First, there were a lot of inaccuracies and the article felt outdated in respect to Scratch 3. Additionally, the article's subject could be broadened to cover other methods and blocks that aren't loops (but still yield). I'm now less opposed to the article's existence but it still needs work.
Awesome-llama (talk | contribs) 15:13, 3 May 2026 (UTC)
