Discuss Scratch

MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

broadcast [message1 v] to [Sprite1 v] :: events
broadcast [message1 v] to [all v] :: events
broadcast [message1 v] to [Sprite1 v] and wait :: events
You should change the broadcasts blocks to have a second dropdown, for sending a broadcast to a specific sprite.
It could be useful, even if there's a workaround. There's no downside to adding this.

Options for 2nd dropdown:
all - sends broadcast to all sprites
name of a sprite - sends a broadcast to that specific sprite
myself - sends a broadcast only to the sprite that sent the broadcast
stage - sends a broadcast to the stage

Last edited by MrFluffyPenguins (Sept. 21, 2020 12:55:37)

fdreerf
Scratcher
1000+ posts

Improving broadcasts

One of the options should be “myself”.
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

fdreerf wrote:

One of the options should be “myself”.
added that to op
scratchastroLOL
Scratcher
1000+ posts

Improving broadcasts

What about the stage?
p-p-p-p-p-p-p-p-p-p-
Scratcher
1000+ posts

Improving broadcasts

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
fdreerf
Scratcher
1000+ posts

Improving broadcasts

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
It's literally a dropdown menu.
ThatOneWeirdDude
Scratcher
1000+ posts

Improving broadcasts

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
I don't know, maybe the point is to make it easier for kids to learn to code?

aka the sole purpose of scratch

Last edited by ThatOneWeirdDude (Sept. 15, 2020 15:14:01)

BobzGamesAlt
Scratcher
500+ posts

Improving broadcasts

Support, I don't see any negatives
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
Couldn't you say that to every suggestion though?

Also… it's just a dropdown. What's the big deal?

Last edited by MrFluffyPenguins (Sept. 15, 2020 15:30:36)

JPOWERPUFFGIRLS
Scratcher
1000+ posts

Improving broadcasts

You could always just
when I receive [ message1]
...
and only one sprite has that, it does the same thing
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

JPOWERPUFFGIRLS wrote:

You could always just
when I receive [ message1]
...
and only one sprite has that, it does the same thing
That works, but then you would have to create a lot more broadcasts.
JPOWERPUFFGIRLS
Scratcher
1000+ posts

Improving broadcasts

Mr_PenguinAlex wrote:

JPOWERPUFFGIRLS wrote:

You could always just
when I receive [ message1]
...
and only one sprite has that, it does the same thing
That works, but then you would have to create a lot more broadcasts.
not really

Sprite 1
when I receive [ hello]
say [Hello]
Sprite 2
when I receive [ hello]
say [Bonjour]
Sprite 3
when I receive [ hello]
say [Ciao]

All 3 sprites would do different functions, using the same message
fdreerf
Scratcher
1000+ posts

Improving broadcasts

JPOWERPUFFGIRLS wrote:

Mr_PenguinAlex wrote:

JPOWERPUFFGIRLS wrote:

You could always just
when I receive [ message1]
...
and only one sprite has that, it does the same thing
That works, but then you would have to create a lot more broadcasts.
not really

Sprite 1
when I receive [ hello]
say [Hello]
Sprite 2
when I receive [ hello]
say [Bonjour]
Sprite 3
when I receive [ hello]
say [Ciao]

All 3 sprites would do different functions, using the same message
But they would all fire at the same time. If you wanted to be economical and use one message and send it at different sprites, you'd need this suggestion.
JPOWERPUFFGIRLS
Scratcher
1000+ posts

Improving broadcasts

fdreerf wrote:

JPOWERPUFFGIRLS wrote:

Mr_PenguinAlex wrote:

JPOWERPUFFGIRLS wrote:

You could always just
when I receive [ message1]
...
and only one sprite has that, it does the same thing
That works, but then you would have to create a lot more broadcasts.
not really

Sprite 1
when I receive [ hello]
say [Hello]
Sprite 2
when I receive [ hello]
say [Bonjour]
Sprite 3
when I receive [ hello]
say [Ciao]

All 3 sprites would do different functions, using the same message
But they would all fire at the same time. If you wanted to be economical and use one message and send it at different sprites, you'd need this suggestion.
or just
Sprite 1
when I receive [ hello]
say [Hello]
Sprite 2
when I receive [ hello]
wait (1) secs
say [Bonjour]
Sprite 3
when I receive [ hello]
wait (2) secs
say [Ciao]
fdreerf
Scratcher
1000+ posts

Improving broadcasts

JPOWERPUFFGIRLS wrote:

or just
Sprite 1
when I receive [ hello]
say [Hello]
Sprite 2
when I receive [ hello]
wait (1) secs
say [Bonjour]
Sprite 3
when I receive [ hello]
wait (2) secs
say [Ciao]
They all fire at the same, just delayed.
What if you wanted this script with only one message?
if <...> then 
broadcast [send to sprite1 v]
else
broadcast [sent to sprite2 v]
end
SquirreIstar
Scratcher
1000+ posts

Improving broadcasts

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
Then why do we have
change [var v] by ()
? It has a very simple workaround that is primarily used in most programming languages, and kids could easily figure it out. “No support—it would make things too easy” is one of my top least favourite things to read on the forums.
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

SquirreIstar wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
Then why do we have
change [var v] by ()
? It has a very simple workaround that is primarily used in most programming languages, and kids could easily figure it out. “No support—it would make things too easy” is one of my top least favourite things to read on the forums.
yeah, scratch is meant to be an introduction to programming- not to be a challenge or make you think outside the box whenever something is inconvenient
SquirreIstar
Scratcher
1000+ posts

Improving broadcasts

Mr_PenguinAlex wrote:

SquirreIstar wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

I don't support because scratch is a place to be creative so if you find an obstacle, you could think outside the box. If everything is lying out for us, what is the point?
Then why do we have
change [var v] by ()
? It has a very simple workaround that is primarily used in most programming languages, and kids could easily figure it out. “No support—it would make things too easy” is one of my top least favourite things to read on the forums.
yeah, scratch is meant to be an introduction to programming- not to be a challenge or make you think outside the box whenever something is inconvenient
exactly!

Last edited by SquirreIstar (Sept. 15, 2020 20:42:29)

panda-wat
Scratcher
100+ posts

Improving broadcasts

this is easily worked around. make multiple messages.
MrFluffyPenguins
Scratcher
1000+ posts

Improving broadcasts

panda-wat wrote:

this is easily worked around. make multiple messages.
you didn't read the op at all did you

Powered by DjangoBB