When you make a custom block, one of the advanced options is “Run without screen refresh”. What does that do?

Normally, after each iteration of a control structure (like <forever> or <repeat ()>) Scratch stops executing the current script and goes on to the next one (this is called yielding). When it has finished executing one iteration of the rest of the scripts, it refreshes the screen (i.e. redraws the sprites in their new positions with their new attributes). It then repeats this process until it finishes executing the control structure.

“Run without screen refresh” causes a custom block to run all at once and not refresh the screen until it has finished executing. This is useful if you want to prevent the flickering that often results when, e.g., you loop through a list and draw each element.

its like running in turbo mode

wow outposted by 4 seconds

Wes64
its like running in turbo mode

Not quite. Turbo mode does as many cycles as possible in a fixed amount of time, then refreshes the screen. Run without screen refresh does enough cycles to exit the block, then refreshes the screen.

nXIII
Normally, after each iteration of a control structure (like <forever> or <repeat ()>) Scratch stops executing the current script and goes on to the next one (this is called yielding). When it has finished executing one iteration of the rest of the scripts, it refreshes the screen (i.e. redraws the sprites in their new positions with their new attributes). It then repeats this process until it finishes executing the control structure.“Run without screen refresh” causes a custom block to run all at once and not refresh the screen until it has finished executing. This is useful if you want to prevent the flickering that often results when, e.g., you loop through a list and draw each element.

Thanks, that helps.

Mega bump. This was the oldest topic in the whole section…

sccar3 wrote:

When you make a custom block, one of the advanced options is “Run without screen refresh”. What does that do?

Well, anyways, the run without screen refresh is a feature that you can put on your custom blocks. Without it on, the screen will refresh itself before running the block again. With it on, the screen won't refresh and it will run the custom block automatically again, so it will make it faster. I always turn that option on when I make custom blocks. Especially if you are doing a pen rendered project, everything should have run without screen refresh. I hope I helped!

derpmeup wrote:

Mega bump. This was the oldest topic in the whole section…

Please don't necrobump topics that seem no longer relevant or answered.

Sonickyle wrote:

derpmeup wrote:

Mega bump. This was the oldest topic in the whole section…

Please don't necrobump topics that seem no longer relevant or answered.

It is still relevant, however. Some Scratchers do not know the difference between Turbo Mode and ‘run without screen refresh’.

sccar3 wrote:

When you make a custom block, one of the advanced options is “Run without screen refresh”. What does that do?

What it does is does the block without refreshing the screen. The screen is going to run this script without the refreshing of the screen if the setting is enabled.

define move
move (pick random (1) to (10)) steps

when you click the stop button It's still runs if you tick it

... {... :: hat control} :: hat control // I bet you can't do that
... (... :: cap control) :: cap control // I bet you can't do that 

if <(username) = [12424]> then
I will help you :: list   
else
Ask (username) :: list
end

12424 wrote:

when you click the stop button It's still runs if you tick it

Please don't necropost