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

MrFluffyPenguins

removed because i hate scratchblocks tag

Last edited by MrFluffyPenguins (Sept. 14, 2020 17:01:55)

xXRedTheCoderXx

Mr_PenguinAlex wrote:
this is the block from snap, its exactly what you want, right

Well, remember what apple502j said:

apple502j wrote:
Note that Snap! and Scratch 3.0 are totally different. I believe it's based on Scratch 1.4?

-1s1s-

As an account made for 1s1s projects (1 Script 1 Sprite, for anybody who doesn't know), this would be extremely useful for me!

FULL SUPPORT!!!

xXRedTheCoderXx

-1s1s- wrote:
As an account made for 1s1s projects (1 Script 1 Sprite, for anybody who doesn't know), this would be extremely useful for me!

FULL SUPPORT!!!

Oh yeah, I never thought of that. XD 1s1s projects would me so much easier with this block. XD

lm1996

I haven't read any other pages, but large support!
Broadcasts are too annoying.

gosoccerboy5

This is essentially the

launch {
script::motion
}::control

block from Snap!. It launches a script that runs while you run other scripts.
(Technically, it looks like

launch ({script::motion}::grey ring)::control

but Scratch isn't ready for grey rings)
So, no support. I'm going for a launch block.

BasisEssence779

I LOVE THIS TOPIC!!!

MeIzAwezomeDede

Support, it would just be useful for countless reasons.
h

Ech0Zero

I very much support this!! i actually made my own topic about this, before i found out it was a dupe. I have some concept art of the block.
it looks more like a [[ block more than an E block though..

gosoccerboy5

I'm confused, why would this be better than a

launch {
}::control

block?

MrFluffyPenguins

gosoccerboy5 wrote:
I'm confused, why would this be better than a
launch {
}::control
block?

Much easier to tell what it does for beginners.

gosoccerboy5

Well, that makes sense. A grudging support “in the name of Scratch” for the OP's suggestion because the (launch) block would be “too confusing for beginners”

Last edited by gosoccerboy5 (Dec. 9, 2020 21:01:18)

-CloudGate-

there was an all at once block once, and it did the same thing as the present run with out screen refresh block

-CloudGate-

https://scratch.mit.edu/discuss/post/2050541/ OMG I FOUND A A GRIFFPATCH POST WITH A WORKAROUND

NanoPIex

NO SUPPORT!!!!!!!!!!!!!!!!! JUST DO 2 SEPERATE SCRIPTS!

PkmnQ

NanoPIex wrote:
NO SUPPORT!!!!!!!!!!!!!!!!! JUST DO 2 SEPERATE SCRIPTS!

Ahem, custom blocks.

define some custom block
do {
. . .
} while doing {
. . .
} :: control

gosoccerboy5

Question: does the “do” script end then the “while doing” script ends? Or vice versa? Or they continue regardless of whether the other script has ended?

Last edited by gosoccerboy5 (Dec. 9, 2020 23:38:33)

PkmnQ

apple502j wrote:
Technically Impossible.
To have multiple scripts run at the same time, we need to use new threads. That's what broadcasts do - each broadcast receiver has its own thread. Custom blocks don't use threads - it runs in the context of parent thread. In the different thread, you cannot access thread variables (aka custom block arguments). Also, we need to wait until all thread finishes executing so we need to yield. Hey, I re-designed “broadcasts”, right?

Also, thread's top block needs to be a hat block, and needs to have set opcodes, not just arbitrary command block. This makes it impossible to use the argument as a thread.

Well, why not rework the custom block system? Maybe when Better Custom Blocks is implemented? This suggestion is useful enough to wait an indefinite amount of time.

PkmnQ

gosoccerboy5 wrote:
Question: does the “do” script end then the “while doing” script ends? Or vice versa? Or they continue regardless of whether the other script has ended?

I think they'll continue, but the scripts ending when the other does might be useful if one of the scripts does nothing.

MeIzAwezomeDede

NanoPIex wrote:
NO SUPPORT!!!!!!!!!!!!!!!!! JUST DO 2 SEPERATE SCRIPTS!

As stated atleast once every page, this doesn't work with custom blocks

Discuss Scratch