miniepicness wrote:

the2000 wrote:

miniepicness wrote:

yeah it isn't close enough. that is run from (treat this script as it came from that sprite) while this is run on (run this code on these sprites like it's a broadcast)

Aren't those the same thing?

Run from would be stealing a script from another sprite and running it here. Run on would be giving a sprite a script and making it run it there.
If the older suggestion was accepted, this one would have a workaround by pasting a run from script in multiple sprites, instead of a run on script in just one sprite

Oh, I get it now. I don't know why I didn't figure that out at first

Monna-Uka wrote:

The idea on OP is kinda weird. I prefer -EmeraldThunder-'s design, though I don't even know if the Snap! arrows would be added to Scratch.
Also, this looks exactly like broadcasts at higher level, so I don't think I'd leave a support here.

There's a suggestion for that and I'd say that suggestion was pretty successful.

Pros:

• Prettier syntax for an extremely specific kind of message where all recipients do the exact same thing
  

Cons:

• Understanding code becomes much more difficult: the code that controls one sprite could be in a completely different sprite
  
• Unclear how private variables, custom blocks, etc, should be handled
  
• Takes up space in the editor
  
• Does nothing that can't be done with messages
  

Overall, I'm against it.

Bump. If I put an empty tag it doesn't work? Or people aren't noticing?

AidyGamer60 wrote:

Bump. If I put an empty tag it doesn't work? Or people aren't noticing?

it works, it's just people don't always post

AidyGamer60 wrote:

Bump. If I put an empty tag it doesn't work? Or people aren't noticing?

Yeah sometimes there just isn't much more to say. Also, normally you just say bump, instead of posting an empty message. It doesn't really matter, it's just sort of the way things work on the forums.

Greg8128 wrote:

Pros:

• Prettier syntax for an extremely specific kind of message where all recipients do the exact same thing
  

Cons:

• Understanding code becomes much more difficult: the code that controls one sprite could be in a completely different sprite
  
• Unclear how private variables, custom blocks, etc, should be handled
  
• Takes up space in the editor
  
• Does nothing that can't be done with messages
  

Overall, I'm against it.

Oh dear I hadn't even thought of custom blocks and local/private variables!

…

Actually though that's a feature that this block would have that the broadcast doesn't. This would let an outside sprite execute code for a custom block in another sprite! I could see that being really useful, although it's probably not the most intuitive way to share custom blocks between sprites (I still really want global/public custom blocks).

AidyGamer60 wrote:

Bump. If I put an empty tag it doesn't work? Or people aren't noticing?

I don't have anything more to talk about, so I do view the topic, but I don't post anything.

Support, but I would add a Clones thing to the first dropdown.

would this be a list of suggestions, i wouldn't want to be (U spent so long on it) but it might

PGBFLITE6373 wrote:

would this be a list of suggestions, i wouldn't want to be (U spent so long on it) but it might

Uh… how?

the2000 wrote:

PGBFLITE6373 wrote:

would this be a list of suggestions, i wouldn't want to be (U spent so long on it) but it might

Uh… how?

you know suggesting multiple thing, however i could be wrong and i hope i am

PGBFLITE6373 wrote:

the2000 wrote:

PGBFLITE6373 wrote:

would this be a list of suggestions, i wouldn't want to be (U spent so long on it) but it might

Uh… how?

you know suggesting multiple thing, however i could be wrong and i hope i am

Point to where in the OP they suggest more than one thing.

the2000 wrote:

PGBFLITE6373 wrote:

the2000 wrote:

PGBFLITE6373 wrote:

would this be a list of suggestions, i wouldn't want to be (U spent so long on it) but it might

Uh… how?

you know suggesting multiple thing, however i could be wrong and i hope i am

Point to where in the OP they suggest more than one thing.

i saw something, idk what tho and im wrong

I think a

tell [sprite1 v] to {
...
} :: control

block would be a much more convenient setup, like the one in Snap!