<switch to costume[ I think that Scratch 2.0 should have a When { } Broadcasted/Received. It has something happen after you broadcast or receive a message.
So do it and I'll be as cool as a cucumber!
Offline
princeeric wrote:
<switch to costume[ I think that Scratch 2.0 should have a When { } Broadcasted/Received. It has something happen after you broadcast or receive a message.
![]()
So do it and I'll be as cool as a cucumber!![]()
+1
Yea, we really need this. I get tired of having to workaround it.
Offline
Offline
The block you seem to be suggesting is already in Scratch: the "When I receive ___" hat block. (See scimonster's post for an image of the block.) When ever a given broadcast is sent out, the scripts under the corresponding "when I receive" block(s) will activate. For example.
sprite1's script: when green flag clicked Forever if touching sprite1 Broadcast contact Stage's script: When I receive contact Change background
Offline
I think they mean a normal block, as to fit into a script without making variables etc
Offline
veggieman001 wrote:
Oh, so you mean <recieved?>
wait until [broadcast] received
Offline
When Broadcast Received is the same thing.
Offline
veggieman001 wrote:
When Broadcast Received is the same thing.
yes but that goes at the top of the script
Offline
I don't see why you would need it otherwise.
Offline
for a lot of things, I've needed it once or twice
Offline
veggieman001 wrote:
Example?
I needed it... can't remember how many times! Anyway, here's the link to the suggestion
Offline
veggieman001 wrote:
Example?
how old are you? like 10? your logic is really bad.
Offline
jji7skyline wrote:
veggieman001 wrote:
Example?
I needed it... can't remember how many times! Anyway, here's the link to the suggestion
There have actually been quite a few times that I would have found this useful too, and unlike a <broadcast received> boolean, I can't see any technical reason it couldn't be done. I think it's a good idea, assuming that's what OP was talking about.
Offline
jslomba wrote:
guys, just use variables.
they're annoying as you end up with over 40 just to do stuff which shouldn't need them
Offline
my-chemical-romance wrote:
veggieman001 wrote:
Example?
how old are you? like 10? your logic is really bad.
He's 13 I think.
And he is one of those people who think that they should completely remove broadcast blocks :c
Offline
puppetadventurer wrote:
my-chemical-romance wrote:
veggieman001 wrote:
Example?
how old are you? like 10? your logic is really bad.
He's 13 I think.
And he is one of those people who think that they should completely remove broadcast blocks :c
I'm 14 and my logic makes sense to loads of people, also I don't disagree with everything someone says.
Offline
<when I receive[
<switch to costume[
tada
Last edited by silentslayer7 (2011-07-22 11:55:56)
Offline
silentslayer7 wrote:
<when I receive[
<switch to costume[
tada
Can you not read? We don't want another hat block, jesus.
Offline
puppetadventurer wrote:
my-chemical-romance wrote:
veggieman001 wrote:
Example?
how old are you? like 10? your logic is really bad.
He's 13 I think.
And he is one of those people who think that they should completely remove broadcast blocks :c
You only think your brother is 13?
Why remove them, veggie?
Offline
guys, a broadcast is an event, not a condition. it would only be true for less than a millisecond.
but scratch COULD have a [broadcast and save [ ]] and a (last saved broadcast) block. that way, you could do
<when green flag clicked>
<repeat until><( last saved broadcast <=> stop )>
<move( 10 )steps>
<next costume>
<end>
Last edited by jslomba (2011-07-27 14:26:01)
Offline