Scratch

turkey3 wrote:

This is possible and has been suggested so many times.You do this:

When I receive [broadcast v]
Set [variable v] to (1)

Then do this:

When gf clicked
Repeat until <(variable) = [1]>
Action goes here
End
More action // this is after its broadcasted

I know, but this would be shorter.

RedRocker227 wrote:

How can the opening post be a necropost?

Not gonna happen. What's wrong with

when I receive [KITTEHS v]

?

(Yay for randomness)

The wait until I receive can be in the middle of a script,

RedRocker227 wrote:

ImagineIt wrote:

RedRocker227 wrote:

How can the opening post be a necropost?

Not gonna happen. What's wrong with

when I receive [KITTEHS v]

?

(Yay for randomness)

The wait until I receive can be in the middle of a script,

But what advantages would there be?

You can have something do something, stop and then wait until something is broadcasted.

RedRocker227 wrote:

ImagineIt wrote:

RedRocker227 wrote:

But what advantages would there be?

You can have something do something, stop and then wait until something is broadcasted.

I guess, but it's not really essential. You could easily do that with variables.

EDIT: My 8,000th post        

Yeah, but many new scratchers would find it easier.

 
wait until <(adf;lkg;alkjf)=(whatever)> 

ImagineIt wrote:

RedRocker227 wrote:

ImagineIt wrote:

You can have something do something, stop and then wait until something is broadcasted.

I guess, but it's not really essential. You could easily do that with variables.

EDIT: My 8,000th post        

Yeah, but many new scratchers would find it easier.

There is no equivalent of it in other programming languages. Broadcasts are events, and events trigger things not control code structure.

I agree. It is possible, but a newer version of Scratch should have a

[scratchblocks]
<I receive [broadcast v]>
[\scratchblocks]

block so that you can put it in to "wait until" blocks.

I have done the thing that is in the first post, but it can get very tedious.