Run without screen refresh {} :: grey

I would like this block for scratch, every time I want code to run without screen refresh I have to make a custom block, which i do not want for some code now and then.

This is inspired by the warp block off Snap!

warp {} :: grey

I like this idea! Although the workaround is pretty easy and compact, it could be useful and would certainly be fun to play with! What block category would it be in? Control?

Run without screen refresh {
...
}::control

Like that ^? Or a different category?

whiteandblackcat wrote:

I like this idea! Although the workaround is pretty easy and compact, it could be useful and would certainly be fun to play with! What block category would it be in? Control?

Run without screen refresh {
...
}::control

Like that ^? Or a different category?

Hmmm.
My Blocks:

Run without screen refresh {} :: custom

Control:

Run without screen refresh {} :: control

I think my blocks because when you build a block it has the option to run without screen refresh and that relates.
Or the control for other reasons

danielthebanana4 wrote:

whiteandblackcat wrote:

I like this idea! Although the workaround is pretty easy and compact, it could be useful and would certainly be fun to play with! What block category would it be in? Control?

Run without screen refresh {
...
}::control

Like that ^? Or a different category?

Hmmm.
My Blocks:

Run without screen refresh {} :: custom

Control:

Run without screen refresh {} :: control

I think my blocks because when you build a block it has the option to run without screen refresh and that relates.
Or the control for other reasons

But then people might think they made the block “run without screen refresh” or start asking how you make a custom block in a C shape.

whiteandblackcat wrote:

danielthebanana4 wrote:

whiteandblackcat wrote:

I like this idea! Although the workaround is pretty easy and compact, it could be useful and would certainly be fun to play with! What block category would it be in? Control?

Run without screen refresh {
...
}::control

Like that ^? Or a different category?

Hmmm.
My Blocks:

Run without screen refresh {} :: custom

Control:

Run without screen refresh {} :: control

I think my blocks because when you build a block it has the option to run without screen refresh and that relates.
Or the control for other reasons

But then people might think they made the block “run without screen refresh” or start asking how you make a custom block in a C shape.

Hmm good point

Maybe it could go in the pen section, since it would most likely be used with pen? I still think the best option would be control, but it has a lot of potential to confuse new scratchers….

A block like this appeared during the development of Scratch 2.0, called “all at once” or “warp speed”. It appeared in the control blocks. I'm not exactly sure why it was removed, though it was made up for by adding a “Run without screen refresh” checkbox onto custom blocks. While the workaround of putting scripts in unrefreshing custom blocks can work if used sparingly, it may become messy if you make a project involving many of them.

As for possible New Scratcher confusion, the checkbox in custom blocks isn't exactly explained as well. However, looking at the Scratch Wiki could help, or asking a question in the forums about it. There are probably other blocks that can be confusing to other New Scratchers, like this block.

(() mod ())

In short, I support adding the block back.

da-maker wrote:

I support adding the block back.

Yeah

da-maker wrote:

As for possible New Scratcher confusion, the checkbox in custom blocks isn't exactly explained as well. However, looking at the Scratch Wiki could help, or asking a question in the forums about it. There are probably other blocks that can be confusing to other New Scratchers, like this block.

They need to also bring back the help guide for the blocks. They had it in 1.4 and 2.0 but why not 3.0?

danielthebanana4 wrote:

They need to also bring back the help guide for the blocks. They had it in 1.4 and 2.0 but why not 3.0?

I forgot to mention that, but I relied on that help guide on blocks that I didn't know how they worked. This includes that said block. Although it's a separate suggestion itself, I do think that the help guide for blocks should be brought back, or at the very least a more accessible method of reaching the Scratch Wiki.

Of course, if New Scratchers regularly know about the wiki though, then that previous statement doesn't matter.

You can do this when cou create a new block! There's a checkbox, under the add parameters thing.

HTML-Fan wrote:

You can do this when cou create a new block! There's a checkbox.

I know that, but the point is I don't want it to be in a custom block.

But it's really easy! We don't need something extra for this. For my signature project I just did this:

define loop
when green flag clicked
forever
loop
end

HTML-Fan wrote:

You can do this when cou create a new block! There's a checkbox, under the add parameters thing.

Yep, which is part of the reason I'm hesitant to support this; it's a neat idea but pretty pointless.

whiteandblackcat wrote:

it's a neat idea but pretty pointless.

Yep. You just copy the specific code over to a block and insert the block execution at this point where you took the code from. If it would be a C block, it wouldn't be much easier.

So, not really support.

Semi-Support. I think this could be helpful with stuff that uses the run without screen refresh where you don't want to use a custom block, but there aren't really that many uses that requires you to not use the “run without screen refresh” without a custom block.

Actually, you can just loop a custom fast block with a normal forever block, and there you have your 60 fps. It's not really useful and custom blocks are never bad, they help organizing code.

This did exist during Scratch 2.0 development (called “all at once”) but it was removed and I see no reason not to add it back. It's annoying when I have to write code like this:

when I receive [message v]
handle message :: custom

define handle message
// runs without screen refresh
...

if I could do this:

when I receive [message v]
all at once {
...
} :: control

I think it's not really annoying and it helps organizing the code, as I said. And it's not so self-explaining as “forever” ur “repeat until” is, so it could confuse beginners.

An idea: You can make any hat block run without a screen refrech like you could with a custom block (by right-clicking on them) and there will also be a little icon when it's enabled.

HTML-Fan wrote:

it helps organizing the code

Not necessarily. If you have lots of custom blocks, this clutters the palette.

Maximouse wrote:

HTML-Fan wrote:

it helps organizing the code

Not necessarily. If you have lots of custom blocks, this clutters the palette.

Well, it's more or less the equivalent to functions in C++. And in my snake project it was useful to have them so I knew where to find the collision detection and where the drawing.

And, really, where do you jump so fast and often between those two that it makes sense? Of course, it makes no sense to make a custom block with 5 blocks so it runs faster, but where does that happen?