Scratch

boolean broadcasts

cheese wrote:

cheese rocks

apple wrote:

apples rock

glitch with bbc code

Last edited by golfer3 (2009-03-01 08:38:26)

demosthenes wrote:

yambanshee wrote:

boolean broadcasts

They haven't strictly said no to that..

They have said that broadcasts arent booleans. Or at lest someone told me that they said it

jamie wrote:

Running Scratch projects as standalone applications:
In most cases, this would hide the source code, breaking the license.

Could You Give Out The Source Code and then would that break the license?

coolstuff wrote:

<if I receive> won't happen.

It can be boolean! It would say yes or no if it's been broadcasted! And if you heard that it won't happen from Archmage, he would rather use 2 or more scripts instead of 1 block!

Yes, I totaly agree with this! If I was the scratch team I think I would get pretty annoyed.

BWOG wrote:

coolstuff wrote:

<if I receive> won't happen.

It can be boolean! It would say yes or no if it's been broadcasted! And if you heard that it won't happen from Archmage, he would rather use 2 or more scripts instead of 1 block!

<when I receive[ broadcast
<set{ boolean  }to(1
<wait( .1 )secsc>
<set{ boolean  }to(0

There is your boolean broadcast.

Things like this should not be true or false though. It would mess you up when you try to use functions in other languages.

Also about your other statement, I try to have my code as compact as possible actually.
When possible, like with the move to x,y block, I try to use as few blocks as possible. Sometimes it appears that I use too much code but this is usually for added functionality or to make it easier to program.