"Run, and run" E block (READ THE ENTIRE OP BEFORE POSTING)

j3r0_plays

But i still wont see how this is useful by any means.. There is a workaround, that works 99% of the time. You reallly dont need this dont you?

Zelfen

Support! I always have to use two scripts for things to happen at the same time… XD

geometric_ghast

There is a workaround, but otherwise this would be a great new block! Support

xXRedTheCoderXx

bump

(but what is there to add to the discussion? idk)

Last edited by xXRedTheCoderXx (Aug. 10, 2020 23:29:25)

BosenChang

geometric_ghast wrote:
There is a workaround, but otherwise this would be a great new block! Support

Can anyone please read this post before replying?

xXTheRedCoderXx wrote:
Well, okay, sure, you could do that, but what about when you CAN'T do two scripts?
Yup! I'm talking about custom blocks!
define Jump
There are many times you'd need two scripts in a custom block, but it only lets you do one script, because you can't put multiple define hats of the same custom block! This would fix that.
define Jump
run {...}while running{...}::control

Why won't just anyone listen?

Last edited by BosenChang (Aug. 11, 2020 00:28:50)

-Rex-

Maximouse wrote:
scratch978654 wrote:
Actually you can still use broadcasts in CBs.
Yes, but
“when I receive” blocks have to be outside the custom block;
if it's run without screen refresh, broadcasts will run after the block returns.

If a custom block runs without screen refresh, the suggested block wouldn’t work anyway.

Maximouse

-Rex- wrote:
If a custom block runs without screen refresh, the suggested block wouldn’t work anyway.

Why?

-Rex-

Maximouse wrote:
-Rex- wrote:
If a custom block runs without screen refresh, the suggested block wouldn’t work anyway.
Why?

Because scripts won’t normally yield when in a non-refresh custom block (except in certain edge cases).

Maximouse

-Rex- wrote:
Because scripts won’t normally yield when in a non-refresh custom block (except in certain edge cases).

OK, I understand now – it isn't needed in run without screen refresh. Yes, you are right.

Zelfen

It would be cool if you could add more bits to it with a button, like this:

run{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}::control

heehee big blocc

fdreerf

-Rex- wrote:
fdreerf wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Do you hate convenience or something?
In what practical situation would this block be convenient?

You already have a ton of broadcasts and would like to not clutter up the list with more broadcasts

Last edited by fdreerf (Aug. 12, 2020 18:03:20)

BosenChang

fdreerf wrote:
-Rex- wrote:
fdreerf wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Do you hate convenience or something?
In what practical situation would this block be convenient?
You already have a ton of broadcasts and would like to not clutter up the list with more broadcasts

[quietly]Why don't we get back more on-topic?[/quietly]

-Rex-

fdreerf wrote:
-Rex- wrote:
fdreerf wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Do you hate convenience or something?
In what practical situation would this block be convenient?
You already have a ton of broadcasts and would like to not clutter up the list with more broadcasts

I’ve never run into that situation even when I’ve had many broadcasts in a project.

fdreerf

-Rex- wrote:
fdreerf wrote:
-Rex- wrote:
fdreerf wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Do you hate convenience or something?
In what practical situation would this block be convenient?
You already have a ton of broadcasts and would like to not clutter up the list with more broadcasts
I’ve never run into that situation even when I’ve had many broadcasts in a project.

You might not, but others will.

-Rex-

fdreerf wrote:
-Rex- wrote:
fdreerf wrote:
-Rex- wrote:
fdreerf wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Do you hate convenience or something?
In what practical situation would this block be convenient?
You already have a ton of broadcasts and would like to not clutter up the list with more broadcasts
I’ve never run into that situation even when I’ve had many broadcasts in a project.
You might not, but others will.

There will almost always be some small number of users who might benefit from a suggestion. There is nothing particularly useful about this suggestion that I can see.

lapisi

Zelfen wrote:
It would be cool if you could add more bits to it with a button, like this:
~snip~

or just put more of the block inside of the block, like this:

run{...}while running{run{}while running{} ::control} ::control

MrFluffyPenguins

-Rex- wrote:
There will almost always be some small number of users who might benefit from a suggestion. There is nothing particularly useful about this suggestion that I can see.

A lot of people supported this suggestion, so clearly people will benefit from this.
And just because you never had an issue with a large number of broadcasts doesn't mean no one else will?

Last edited by MrFluffyPenguins (Aug. 12, 2020 22:52:01)

xXRedTheCoderXx

-Rex- wrote:
There is nothing particularly useful about this suggestion that I can see.

Hmm…, in that case, maybe try reading some of the posts that say how this would be super useful for a project they're making. This is one of them

:

coder2045 wrote:
Support. I've had to use eight broadcasts and ten scripts in an animation just to have characters fight over a paper airplane and I could just do:
set [marker v] to [0]
run{
line 1:: #0000dd
set [marker v] to [1]
}while running{
run{
wait until <(marker) = [1]>
line 2:: #f00000
set [marker v] to [2]
}while running{
run{
wait until <(marker) = [2]>
line 3:: #f0f000
set [marker v] to [3]
}while running{
...
}:: control
}:: control
}:: control

-Rex- wrote:
There will almost always be some small number of users who might benefit from a suggestion.

True, but this isn't one of those cases. If you read some more posts, you would find that a lot people would find this useful!

Zelfen wrote:
It would be cool if you could add more bits to it with a button, like this:
run{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}while running{}::control
heehee big blocc

You wouldn't need to do that, just put multiple run while running blocks together like in the OP.

j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.

Woah - did somebody really say that? I can't find the post, so I'm guessing it got deleted. And for good reason, that kinda hurt my feelings. XD Welp, I guess you can't please everybody.

geometric_ghast

xXRedTheCoderXx wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Woah - did somebody really say that? I can't find the post, so I'm guessing it got deleted. And for good reason, that kinda hurt my feelings. XD Welp, I guess you can't please everybody.

Ya you can't. Sorry that someone said that

MrFluffyPenguins

xXRedTheCoderXx wrote:
j3r0_plays wrote:
Okay, let me say. I ABSOLUTELY HATE THIS IDEA. I am out of here.
Woah - did somebody really say that? I can't find the post, so I'm guessing it got deleted. And for good reason, that kinda hurt my feelings. XD Welp, I guess you can't please everybody.

Yeah, it looks like it got deleted.
new page except i forgot to look at the number and i don't want to edit twice

Last edited by MrFluffyPenguins (Aug. 12, 2020 22:53:20)

Discuss Scratch