"2" is considered False when using AND/OR combinators
Posted: Wed Nov 05, 2025 1:08 pm
This has bugged me for years, I guess it´s intended and not a bug since its pretty obvious, but I dont see the reason for it.
If you make a combinator with for example condition A OR B, it will only consider A as True if it has the value 1. If it has the value 2 or more it is considered False.
It would simplify many of my designs if 2 was considered True.
I think it could work in one of two ways to make sense. I prefer the first, but both is fine.
First acceptable way:
Zero or smaller = False
Bigger then zero = True
Second acceptable way:
0 = False
every other number = True
Is there a reason for the current functionality or am I just the only ones who is disturbed by this?
If you make a combinator with for example condition A OR B, it will only consider A as True if it has the value 1. If it has the value 2 or more it is considered False.
It would simplify many of my designs if 2 was considered True.
I think it could work in one of two ways to make sense. I prefer the first, but both is fine.
First acceptable way:
Zero or smaller = False
Bigger then zero = True
Second acceptable way:
0 = False
every other number = True
Is there a reason for the current functionality or am I just the only ones who is disturbed by this?