Discuss Scratch
- Discussion Forums
- » Suggestions
- » This block would make a lot of things easier...
- ShinySkarmory227
- Scratcher
100+ posts
This block would make a lot of things easier...
Oopsies.
The Block
I saw a topic about this just earlier, it would be a bit simpler, and quicker to use.
Examples of The Block's Use
The Block
<[ ]>Why Do We Want/Need It?
I saw a topic about this just earlier, it would be a bit simpler, and quicker to use.
Examples of The Block's Use
when this sprite clicked
forever
if <(costume #) = [ <[1]> or <[2]>]> then
wait (1) secs
next costume
else
wait (.14) secs
next costume
end
Last edited by ShinySkarmory227 (March 19, 2015 21:23:59)
- Really_A
- Scratcher
1000+ posts
This block would make a lot of things easier...
No support because I think this scripts: Oopsies.
The Block<[ ]>Why Do We Want/Need It?
I saw a topic about this just earlier, it would be a bit simpler, and quicker to use.
Examples of The Block's Usewhen this sprite clicked
forever
if <(costume #) = [ <[1]> or <[2]>]> then
wait (1) secs
next costume
else
wait (.14) secs
next costume
end
if <<(costume #) = [ 1]> or <(costume #) = [2]>> thenIs quite simple. And that's normal for a programming language, such as Phython:
end
if costume = 1 or costume =2:
#do some code
- 3sal2
- Scratcher
100+ posts
This block would make a lot of things easier...
This is totally pointless. This reminds me of a fictitious store chain I made up…
Who would want to cast strings into booleans anyway?! No support.
Who would want to cast strings into booleans anyway?! No support.
- CatsUnited
- Scratcher
1000+ posts
This block would make a lot of things easier...
^ Also, this is what the block looks like… This is totally pointless. This reminds me of a fictitious store chain I made up…
Who would want to cast strings into booleans anyway?! No support.
< [] :: operators>
bottom text
- Letsgopitt
- Scratcher
500+ posts
This block would make a lot of things easier...
No support, it doesn't make sense. The round blocks can be put into strings, and it is just one string that goes inside of a string, making it useless. What uses did you have in mind?
Stop saying that something could potentially confuse a New Scratcher as justification of saying No Support!
This is the B-est of B-sides.
Hope you had to wait in a long line.
We never even played this song live.
This is the B-est of B-sides.
-ʎɥsols
- 3sal2
- Scratcher
100+ posts
This block would make a lot of things easier...
No, if you quote it, you can see it's a Boolean block.
< [] :: operators>
[quote=CatsUnited][scratchblocks]< [] :: operators>[/scratchblocks][/quote]
Last edited by 3sal2 (March 20, 2015 20:08:32)
- stickfiregames
- Scratcher
1000+ posts
This block would make a lot of things easier...
So you want to be able to make this?
<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of
<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
Last edited by stickfiregames (March 20, 2015 21:35:57)
- GyroscopeBill
- Scratcher
500+ posts
This block would make a lot of things easier...
The way it is currently set out encourages kids to think in the logical sense needed for programming.
Your suggestion is not even possible or useful.
Sorry, but no support.
Your suggestion is not even possible or useful.
Sorry, but no support.
Pingu is learning about politics with this amazing project.
- Iditaroid
- Scratcher
500+ posts
This block would make a lot of things easier...
Interesting idea but no support! The “or” block only ever returns true or false and trying to get it to do other things through this would just be confusing
If this ends up being too long, i.e. you want to check if the costume is any number between one and ten, you can add the numbers 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10 to a list and just do this
if <<(costume #) = [ 1]> or <(costume #) = [2]>> then
end
If this ends up being too long, i.e. you want to check if the costume is any number between one and ten, you can add the numbers 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10 to a list and just do this
if <[list v] contains (costume #)> then
end
- Letsgopitt
- Scratcher
500+ posts
This block would make a lot of things easier...
Oops, I thought it was a string. Still, no support as per the points made by previous posters.
Stop saying that something could potentially confuse a New Scratcher as justification of saying No Support!
This is the B-est of B-sides.
Hope you had to wait in a long line.
We never even played this song live.
This is the B-est of B-sides.
-ʎɥsols
- UndeadSorcerer
- Scratcher
100+ posts
This block would make a lot of things easier...
No support. A variable can be used and changed. It is a simple solution. If you really want it to exist he is a script I came up with that works the same.
You can use that without credit if you want. You can also change the number by replacing the 2 with something else.
define number (num)
if <<(costume #) = [1 ]> or <(costume #) = (num)>
Do something
end
when this sprite clicked
forever
number (2) :: custom
end
You can use that without credit if you want. You can also change the number by replacing the 2 with something else.
- childgamer
- Scratcher
59 posts
This block would make a lot of things easier...
So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier
<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a
<() or ()>Block to solve that problem
Last edited by childgamer (March 20, 2015 22:56:45)
________________________________________
l This box is protection from Kumquats—–>l
—————————————————
- stickfiregames
- Scratcher
1000+ posts
This block would make a lot of things easier...
That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problem
- childgamer
- Scratcher
59 posts
This block would make a lot of things easier...
It would still work, because the knowledge in question is either 1 or 2 would work.That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problem
when green flag clicked
forever
if <(some random varible) = [<<[1]::operators> or <[2]::operators>>]> then
do some random stuff
end
end
Last edited by childgamer (March 21, 2015 13:48:25)
________________________________________
l This box is protection from Kumquats—–>l
—————————————————
- Iditaroid
- Scratcher
500+ posts
This block would make a lot of things easier...
What happens if you try to do this?It would still work, because the knowledge in question is either 1 or 2 would work.That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problemwhen green flag clicked
forever
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
end
say <(1) or (2)>
- childgamer
- Scratcher
59 posts
This block would make a lot of things easier...
What happens if you try to do this?It would still work, because the knowledge in question is either 1 or 2 would work.That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problemwhen green flag clicked
forever
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
endsay <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off with
say (pick random (1) to (2))
Last edited by childgamer (March 21, 2015 13:51:22)
________________________________________
l This box is protection from Kumquats—–>l
—————————————————
- Iditaroid
- Scratcher
500+ posts
This block would make a lot of things easier...
I feel like this block's function is a bit ambiguous then! Still no support!What happens if you try to do this?It would still work, because the knowledge in question is either 1 or 2 would work.That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problemwhen green flag clicked
forever
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
endsay <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off withsay (pick random (1) to (2))
- childgamer
- Scratcher
59 posts
This block would make a lot of things easier...
Sure, it's not best for everything, but it's a lot simpler this:I feel like this block's function is a bit ambiguous then! Still no support!What happens if you try to do this?It would still work, because the knowledge in question is either 1 or 2 would work.That still wouldn't work because the value of a reporter can't simultaneously be two different things.So you want to be able to make this?<(costume #) = <<[1]::operators> or <[2]::operators>>>No support because it's not possible - what would the value of<<[1]::operators> or <[2]::operators>>be? (it can only be true or false, because it's a boolean)
The value is simutaneously 1 and 2. the value can be 1 or 2 and it still be true. I agree, that the block would make things easier<<<[1]::operators> or <<[2]::operators>or<[4]::operators>>>above shows that the value is simultaneously 1, 2, and 4 all at the same time.
Oh, I just caught that it's a boolean script. Perhaps we should make a<() or ()>Block to solve that problemwhen green flag clicked
forever
if <(some random varible) = [<<[1]::operators> or <<[2]::operators> >> ]> then
do some random stuff
end
endsay <(1) or (2)>
the sprite has a choice of 1 or 2 to say. Here, I'd say that you are just as well off withsay (pick random (1) to (2))
((variable) = ([1] or [2]::operators))than this:
<<(variable) = [1]> or <(variable) = [2]>>
Last edited by childgamer (March 21, 2015 14:05:45)
________________________________________
l This box is protection from Kumquats—–>l
—————————————————
- Discussion Forums
- » Suggestions
- » This block would make a lot of things easier...