Bacteria999 wrote:

super_loro wrote:

when green flag clicked
say [boolean variables?!] for (2) secs
say [YES!!!] for (2) secs
:):)
set [<Yeah!> v] to [boolean]

Scratch Wiki wrote:

Blockspam is a type of forum spam in the form of nonsense, offtopic and long scripts made with the Block Plugin. However, on-topic scripts, such as saying a message with the Say block or using scratchblocks to display an on-topic message is considered a form of speech and is not considered spam.

The Help With Scripts forum has a topic specifically for experimenting with the block plugin, but those who spam elsewhere should be reported.

The old tags were also used to make blockspam.

The Announcements Forum and the New Scratchers Forum are the most vulnerable to blockspam.

Scratch Wiki wrote:

However, on-topic scripts, such as saying a message with the Say block or using scratchblocks to display an on-topic message is considered a form of speech and is not considered spam.

donotforgetmycode wrote:

Everyone is saying “no support” because the workaround is easy, but it's also confusing.

Bluebatstar wrote:

donotforgetmycode wrote:

Everyone is saying “no support” because the workaround is easy, but it's also confusing.

It's really not. Boolean Variables are literally just variables that can only store two inputs. The workaround is unbelievably easy and most people could understand it. It would add absolutely nothing to the website, in my opinion. No support.

theonlygusti wrote:

I think it would be nice to be able to drag variables into boolean slots, and have them be evaluated as booleans implicitly.

<[] = []>

set var1 to [true v] 
<var1>
set var1 to [false v] 

set <you mean like this?> to [0]

my variable ::variables boolean

theevolutionary wrote:

On the topic of booleans:

I understood Scratch was to help make programming concepts and constructs easy to understand/use for a younger audience, and for the most part it does an excellent job.

Booleans are POTENTIALLY complex in application but they are on the idea that something is “true' or ”false'. ‘On’ or ‘Off’. Children understand that concept quite easily. What is HARDER to understand is expressions like “0 = 1” or “1 = 1”. By not having a variable that is “on” or “off” you often force a simple idea into a more abstract one. That is harder for children to understand as opposed to a simple light switch. You allow boolean concepts for sprites which is a good thing, but to not follow through and allow kids to make variables with the idea that something is “on' or ”off“ without sprites gets confusing for children because these things exist in their world.

So respectfully, I disagree that booleans are too 'complex” for children. On the contrary, I believe and have experienced children not understanding why they do not have simple booleans (on/off) variables which forces abstract workarounds to simple ideas in their Scratch “worlds”. Kids understand light switches, they understand the idea of “A” or “B”. By that definition, they already understand the concept of booleans. I would strongly encourage boolean variables with simple “true/false” settings, which maybe should include boolean only comparitors (to reduce programming complexity).

Nuff said. Cheers.

forever
set var1 to <[a]=[a]>
end

<var1>

define set var1 to <var1>

set [foo v] to [1]

set [foo v] to [0]

<(foo) = [1]>

<(foo) = [0]>

dogeiscut wrote:

I don't need this, and it would take up space in the editor. No support, also very easy work around is to just use regular varibles

set [foo v] to [1]

set [foo v] to [0]

<(foo) = [1]>

<(foo) = [0]>

Vibrato wrote:

dogeiscut wrote:

I don't need this, and it would take up space in the editor. No support, also very easy work around is to just use regular varibles

set [foo v] to [1]

set [foo v] to [0]

<(foo) = [1]>

<(foo) = [0]>

everything takes up space in the editor. terrible argument, there

dogeiscut wrote:

I don't need this, and it would take up space in the editor. No support, also very easy work around is to just use regular varibles

set [foo v] to [1]

set [foo v] to [0]

<(foo) = [1]>

<(foo) = [0]>

set [boolean v] to [true] //Statement shows that boolean variable is true.

set [boolean v] to [false] //Statement shows that boolean variable is false.

(boolean) //Dosen't look like a boolean...

boolean ::variables boolean //Like this [I realised you can use ::boolean :O]

dogeiscut wrote:

snip wrote:

ahem



tell this fella the same thing

(this was on a suggestion i made and i was trying to get revenge which i admit is quite stupid of me)

alexphan wrote:

drmcw wrote:

alexphan wrote:

One question: WHAT ARE BOOLEAN VARIABLES???????!?!?!?:o

A variable that can be either true or false. If it was a Scratch block it would have pointy ends.

So that's a boolean variable?
I kind of support because they're timesavers.

There shold be a dropdown, instead of putting strings.

So the block is like this: [set to
false

Then you can put it in a boolean insert, like
if <touching boy?> or
repeat until <touching boy?>

if <[5]=[10]> then 
set [does 5 equal 10? v] to [true]
else
set [does 5 equal 10? v] to [false] 
end

TrainerJaden2 wrote:

alexphan wrote:

drmcw wrote:

alexphan wrote:

One question: WHAT ARE BOOLEAN VARIABLES???????!?!?!?:o

A variable that can be either true or false. If it was a Scratch block it would have pointy ends.

So that's a boolean variable?
I kind of support because they're timesavers.

There shold be a dropdown, instead of putting strings.

So the block is like this: [set to
false

Then you can put it in a boolean insert, like
if <touching boy?> or
repeat until <touching boy?>

another type:

if <[5]=[10]> then 
set [does 5 equal 10? v] to [true]
else
set [does 5 equal 10? v] to [false] 
end

set [Does 5 = 10 v] to <[5] = [10]>

<my boolean::grey> 
<☁ my boolean::grey> 

set [my boolean v] to <>::grey

toggle [my boolean v]::grey

show boolean [my boolean v]::grey

hide boolean [my boolean v]::grey

a_guy_who_made_games wrote:

<my boolean::grey> 
<☁ my boolean::grey> 

set [my boolean v] to <>::grey

toggle [my boolean v]::grey

show boolean [my boolean v]::grey

hide boolean [my boolean v]::grey