I have been having weird things happening with variables accepting hexagonal blocks.
Ex:
<set{ test }to( << <and> >>
Is anyone else having this? I have suspicions that it might be because of this: http://scratch.mit.edu/projects/Surfer123/344381 project experiment, but I can't be sure.
Last edited by shadow_7283 (2008-12-26 09:43:57)
Offline
Well, that's pretty cool...you can set a variable to a boolean value. But you still can't use the variable as a boolean in a conditional so it's still not much help. For instance, you can NOT do this yet:
[blocks]
<if> <{ Flag Variable }>
<end>
[/blocks]
Maybe in release 1.4 we'll get real boolean variables!
Offline
Paddle2See wrote:
Well, that's pretty cool...you can set a variable to a boolean value. But you still can't use the variable as a boolean in a conditional so it's still not much help. For instance, you can NOT do this yet:
[blocks]
<if> <{ Flag Variable }>
<end>
[/blocks]
Maybe in release 1.4 we'll get real boolean variables!
OK I have looked into it further, and the glitch can be fun! I figured out that if you put conditions in there that are true ( <set{ variable }to( <( 0 <=>0 )> ) and it will read true on the display!
Last edited by shadow_7283 (2008-12-26 09:50:06)
Offline