Easier way of combining "Join", "And" and "Or" blocks.

CKCG

bump

TheAdriCoolManDude

space_elephant wrote:
better way:
(join[hello ][world]@addInput::operators)
when you click the arrow, another input is added like this
(join[hello ][world][ from ][high]@delInput@addInput::operators)
if you click the left arrow, then one input will be removed

I rather support this, as it makes it more clear as how the block works (the block itself, not the post). And like the original suggestion, it makes it easier to work with the join block.

Seam49

Support, maybe we could have a right clic and then a button like

number of inputs

And then clickin it pops up a box to do huge numbers quickly.

space_elephant

(sum of()()@addInput::operators)
(product of()()@addInput::operators)
<all of<><>@addInput::operators>
<any of<><>@addInput::operators>
(join[][]@addInput::operators

|
V

(sum of()()()()@delInput@addInput::operators)
(product of()()()()@delInput@addInput::operators)
<all of<><><><>@delInput@addInput::operators>
<any of<><><><>@delInput@addInput::operators>
(join[][][][]@delInput@addInput::operators

space_elephant

would this be available for the + and * blocks?

Harakou

Merged in a duplicate thread.

-ShadowOfTheFuture-

I'm not sure if I've posted on this thread already, but whatever…

Support. This would really help me tidy up my code and prevent the lag that's sometimes caused by massive block stacks.

marioario

Cool idea! Support

maskedmaruder

Support. Some scripts get way too messy.

Cutie_Poochi

when I come::events
if <(lag reduced) > (lag created)> then
change [support v] by ((lag reduced) - (lag created))
end

Last edited by Cutie_Poochi (Nov. 26, 2018 09:47:34)

p-p-p-p-p-p-p-p-p-p-

I have seen that there are things that need a lot of blocks that could be shortened to 1 block. This would allow more room in the area ad less work required. What I am suggesting is a block we already have but an improvement. there are 3 blocks that can use this improvement and they are

(join [] [world])
(letter [] of [world])
<() contains ()? :: operators>

anyways, these blocks have 2 slots in them. If you want more you have to add more blocks. My idea is to update those into these blocks:

<() contains () [or v] () @delInput @addInput :: operators>

When you click on the triangle it adds another input. There's also a function in the middle, which holds or or and.
You can do this up to 30 times. This would improve decoding numbers and other things as well. 1 thing would be

when green flag clicked
ask [give me cordinates ad I will go to that slot! write it like 000 and 000] and wait
go to x: (letters (1) (2) and (3) @delInput @addInput of (answer) :: operators ) y: (letters (9) (10) (11) @delInput @addInput of (answer) :: operators)

The alternative to this would be:

when green flag clicked
ask [give me cordinates ad I will go to that slot! write it like 000 and 000] and wait
go to x: (join(join(letter [1] of (answer)) (letter [2] of (answer))) (letter [3] of (answer))) y: (join(join(letter [6] of (answer)) (letter [7] of (answer))) (letter [8] of (answer)))

This seems more complicated to newer users than the proposed alternative.
Here are all the reasonable examples I could think of:

if <> then  {

}else if <> @delInput @addInput{

}else{
} :: control

<keys [ v] and [ v] pressed? @delInput @addInput ::sensing>
<[] [< v] [] [< v] [] @delInput @addInput::operators>
(() [+ v] () [- v] () @delInput @addInput::operators) // cause of PEMDAS these can be compressed. Could be a little confusing to younger kids, though.
(() [x v] () [/ v] () @delInput @addInput::operators) // same as above.
<<> and <> and <> @delInput @addInput ::operators>
<<> or <> or <> @delInput @addInput ::operators>
(join [] [] [] @delInput @addInput ::operators)
(letters () [through v] () of [] @delInput @addInput ::operators)
add [] and [] to [list v] @delInput @addInput ::list

These blocks could be added in as an extension, so it wouldn't confuse new scratch users.

Last edited by p-p-p-p-p-p-p-p-p-p- (Feb. 3, 2024 16:36:48)

Zelfen

Nice idea, +1 with you there.

scratchastroLOL

Zelfen wrote:
Nice idea, +1 with you there.

and why?

anyways, what about beginners? they can find it confusing.

LandonHarter

join [foo] [bar] [baz] @delInput@addInput :: operators reporter
letters (1) (2) (3) @delInput@addInput of [world] :: operators reporter
[haystack] contains [needle] or [key] or [turkey] @delInput@addInput :: operators boolean

Better concept art

p-p-p-p-p-p-p-p-p-p-

scratchastroLOL wrote:
Zelfen wrote:
Nice idea, +1 with you there.
and why?

anyways, what about beginners? they can find it confusing.

There is that issue but I don't think it is too bad because I'm sure they'll learn. I learned a lot

p-p-p-p-p-p-p-p-p-p-

LandonHarter wrote:

join [foo] [bar] [baz] @delInput@addInput :: operators reporter
letters (1) (2) (3) @delInput@addInput of [world] :: operators reporter
[haystack] contains [needle] or [key] or [turkey] @delInput@addInput :: operators boolean

Better concept art

Thank you!! Do you support? ad also can I quote you and add that?

p-p-p-p-p-p-p-p-p-p-

bump

RedGuy7

bump

Vanilla2011

Great idea! I know what you mean! I've run into these situations before.
+1

Vanilla2011

Cutie_Poochi wrote:

when I come::events
if <(lag reduced) > (lag created)> then
change [support v] by ((lag reduced) - (lag created))
end

Better idea:

when I come::hat events//Replace it with this hat block.
if <(lag reduced) > (lag created)> then
change [support v] by ((lag reduced) - (lag created))
end

Last edited by Vanilla2011 (Sept. 4, 2020 09:02:37)

Discuss Scratch