Discuss Scratch
- Discussion Forums
- » Suggestions
- » Ability to start specific scripts or sprites
- megaman100
-
Scratcher
100+ posts
Ability to start specific scripts or sprites
If we can stop scripts, then we should have a block that can start other scripts.
If you want to know more about adding names to scripts check out my proposal about adding names to scripts here.
start script [script 1 v] in [myself v]:: control
If you want to know more about adding names to scripts check out my proposal about adding names to scripts here.
Last edited by megaman100 (Aug. 24, 2018 20:19:10)
- BestUsernameSoFar
-
Scratcher
100+ posts
Ability to start specific scripts or sprites
How exactly would this work?
- mlcreater
-
Scratcher
1000+ posts
Ability to start specific scripts or sprites
I have approximately five problems with this concept:
1. If Sprite1 runs:start script [script 1 v] in [Sprite2 v]::control,
what should happen if Sprite2 has clones? Should only the original run “script 1”? Should the original and all of its clones do so?
2. I don't believe sprites should be able to control each other.
3. Communication between sprites is why we have broadcasts.
4. If analogous to thestop [ v]block, the start script block would specify three options, all of which I find weird:start [all v]::control//does this mean all scripts (which includes custom blocks), or all green flag scripts?start [this script v]::control//it is already running if it is calling thisstart [other scripts in sprite v]::control//Hmm... if this sprite's “when key [space v] pressed” scripts will run, why not others'?
5. How would one title their scripts?
Scratch cannot do it for them because scripts in a sprite do not necessarily have an order.
- Discussion Forums
- » Suggestions
-
» Ability to start specific scripts or sprites