Pages: 1
Why is it necessary then?
Offline
It's meant so that your scripts are smaller. For example, you could change this:
repeat (10) change [color v] effect by (25) glide (1) secs to x: (2) y: (34) say [Hello!] for (2) secs play sound [Pop v] until done endinto
blockwhich is a lot easier than doing the first script over and over.
Offline
Mokat wrote:
It's meant so that your scripts are smaller. For example, you could change this:
repeat (10) change [color v] effect by (25) glide (1) secs to x: (2) y: (34) say [Hello!] for (2) secs play sound [Pop v] until done endintoblockwhich is a lot easier than doing the first script over and over.
It can also be shared across sprites, reducing the need to duplicate scripts.
Offline
That's the same thing I was thinking! It's pretty much the same as broadcast and wait.
Because here are what is the same:
Define script, (when i receive), and it would pretty much act the same.
I'm not sure but there must be some reason.
Offline
CanadianGeorge wrote:
That's the same thing I was thinking! It's pretty much the same as broadcast and wait.
Because here are what is the same:
Define script, (when i receive), and it would pretty much act the same.
I'm not sure but there must be some reason.
You can make blocks that do not require screen refreshes. Good for terrain generations.
Offline
procedures can be atomic
it is also easier to manage a procedure with arguments instead of a broadcast with many variables.
Offline
Pages: 1