bump

Can you somehow change the block name or something so it doesn't get confused with the 2.0 alpha all at once block?

medians wrote:

Can you somehow change the block name or something so it doesn't get confused with the 2.0 alpha all at once block?

You could suggest one. I don't have any ideas

VedanshS933 wrote:

medians wrote:

Can you somehow change the block name or something so it doesn't get confused with the 2.0 alpha all at once block?

You could suggest one. I don't have any ideas

I'm confused, I was saying to change the name of the block in this topic to prevent confusion with that block. By 2.0 alpha all at once block, I mean the block called all at once (originally warp speed) that used to exist in the Scratch 2.0 alpha.

historical_supa wrote:

This was in 2.0 alpha, but wonder why they removed. This would be better than just telling you to turn on turbo mode, though it could be workarounded with custom blocks with run without screen refresh checked. Just saying.

Late, but that block didn't function the same as this suggestion. all at once/warp speed was replaced with run without screen refresh (though that can cause custom block cluttering).
By the way, this is the confusion that I am talking about.

VedanshS933 wrote:

medians wrote:

Can you somehow change the block name or something so it doesn't get confused with the 2.0 alpha all at once block?

You could suggest one. I don't have any ideas

Hold on, do you mean suggest a new name??
You could do “run at same time” or something, but that's all I can come up with

How would this work? Computers can only do one thing at once, unless you use multiple processor cores or otherwise duplicate hardware (and Scratch does not take advantage of this). One block would have to be run slightly before the other- meaning it would just function like a custom block set to run without screen refresh.

BigNate469 wrote:

How would this work? Computers can only do one thing at once, unless you use multiple processor cores or otherwise duplicate hardware (and Scratch does not take advantage of this). One block would have to be run slightly before the other- meaning it would just function like a custom block set to run without screen refresh.

No, this is different from the block called all at once from the 2.0 alpha
It could act as if you were doing something like this (instead of actually running it at the same exact time):

broadcast [script1 v]
broadcast [script2 v]
broadcast [script3 v]
when I receive [script1 v]
say [Due its content, this project should not be viewed by anyone.] for (2) secs //just like the bamboozlement project
when I receive [script2 v]
play sound [meow v] until done
when I receive [script 3 v]
play sound [pop v] until done

And instead, it would be like this:

all at once {
say [Due its content, this project should not be viewed by anyone.] for (2) secs
play sound [meow v] until done
play sound [pop v] until done
} ::control

medians wrote:

snip

But that doesn't run it at the same exact time- things still happen in an order- so wouldn't that be exactly what the 2.0 alpha block did? Just running it as fast as possible?

BigNate469 wrote:

medians wrote:

snip

But that doesn't run it at the same exact time- things still happen in an order- so wouldn't that be exactly what the 2.0 alpha block did? Just running it as fast as possible?

No, the all at once block did the same thing as run without screen refresh, which lags with the code that I gave, and does not run together..
Also, I really do not think people will notice this though..

What's the point of having the all at once block? Like about 1 million people already have said, just use run without screen refresh. It kind of is a lie though, slow enough scripts(like drawing pen on every pixel on the canvas) will cause screen refreshes and you can see it filling the canvas.

IndexErrorException wrote:

What's the point of having the all at once block? Like about 1 million people already have said, just use run without screen refresh. It kind of is a lie though, slow enough scripts(like drawing pen on every pixel on the canvas) will cause screen refreshes and you can see it filling the canvas.

1. Run without screen refresh can cause custom block clutter, and you might not want to create a custom block just to run one thing without screen refresh. You could just replicate the option if replaced by surrounding the code of the custom block.
2. Please read previous posts on this topic, this block works differently from the all at once block in the 2.0 alpha, which existed before the option.

medians wrote:

IndexErrorException wrote:

What's the point of having the all at once block? Like about 1 million people already have said, just use run without screen refresh. It kind of is a lie though, slow enough scripts(like drawing pen on every pixel on the canvas) will cause screen refreshes and you can see it filling the canvas.

1. Run without screen refresh can cause custom block clutter, and you might not want to create a custom block just to run one thing without screen refresh. You could just replicate the option if replaced by surrounding the code of the custom block.
2. Please read previous posts on this topic, this block works differently from the all at once block in the 2.0 alpha, which existed before the option.

True, I have ran into this problem of the clutter several times, honestly it was never a big deal to me but it's alright, I support the idea for it's ease.

IndexErrorException wrote:

medians wrote:

IndexErrorException wrote:

What's the point of having the all at once block? Like about 1 million people already have said, just use run without screen refresh. It kind of is a lie though, slow enough scripts(like drawing pen on every pixel on the canvas) will cause screen refreshes and you can see it filling the canvas.

1. Run without screen refresh can cause custom block clutter, and you might not want to create a custom block just to run one thing without screen refresh. You could just replicate the option if replaced by surrounding the code of the custom block.
2. Please read previous posts on this topic, this block works differently from the all at once block in the 2.0 alpha, which existed before the option.

True, I have ran into this problem of the clutter several times, honestly it was never a big deal to me but it's alright, I support the idea for it's ease.

I mean, you are looking for a different topic though because this is different from the 2.0 alpha block, as said before and in the original post:
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/post/4371/

VedanshS933 wrote:

PS : Not a Duplicate because this launches two blocks at once but that will make it go at turbo speed like run without screen refresh function in custom blocks

It's still the same concept.

ilovestories wrote:

VedanshS933 wrote:

PS : Not a Duplicate because this launches two blocks at once but that will make it go at turbo speed like run without screen refresh function in custom blocks

It's still the same concept.

No, the other one is run without screen refresh, which lags if you put the code I showed above

bump

bump

By the way the blocks in the original post are currently broken. Try this:

All at Once {

} :: control

If you want cap

All at Once {

} :: control cap

Also, should likely be all lowercase.

medians wrote:

By the way the blocks in the original post are currently broken. Try this:

All at Once {

} :: control

If you want cap

All at Once {

} :: control cap

Also, should likely be all lowercase.

ok thanks