Discuss Scratch

TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bring up my post.
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump!
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump
ThisIsTemp1
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

I support this, would be useful for repeated addition subtraction, rounding etc.
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump
ThisIsTemp1
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

BUMP!
breakfast_for_dinner
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

bringing up this topic
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump
FirstEye
Scratcher
31 posts

Allow changing of how many inputs there are in operator blocks.

W rizz support
han614698
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

FirstEye wrote:

(#29)
W rizz support
You must give a reason to support - you saying support does not matter; the forums are not a polling box.
MonkeyBean2
Scratcher
100+ posts

Allow changing of how many inputs there are in operator blocks.

If this was added it would be nice if you could put a list in there as well to eg. sum up all items in a list
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

MonkeyBean2 wrote:

If this was added it would be nice if you could put a list in there as well to eg. sum up all items in a list
That would be nice; however, it might be asking too much, especially since lists are meant to be the last thing you learn in Scratch, so putting list-related blocks in operators probably isn't the best idea.
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump.

Last edited by TheCreatorOfUnTV (Sept. 15, 2024 05:03:25)

TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

Bump!
ihavenocluewhythisis
Scratcher
500+ posts

Allow changing of how many inputs there are in operator blocks.

medians wrote:

TheCreatorOfUnTV wrote:

medians wrote:

TheCreatorOfUnTV wrote:

medians wrote:

Oh, and, why does the equals block have a dropdown in the original post?
Don't worry, this is not a feature currently in 3.0 but it would go with the dropdown system.
I mean, I don't really usually get the dropdown, since block switching could just be reimplemented outside of the Data category (basically, before 3.0, you could also swap certain operator blocks to other related blocks, and that included the equals block by right clicking, which you can still do currently, but only for variables and lists).
Block switching is not possible on tablets and slightly harder on Chrome Books than on most computers (which is the whole reason Scratch switched to HTML5, NOT because they knew Flash was going to get removed), and the dropdown system would reduce clutter on the blocks page as well as being less confusing for beginners who don't know right-clicking gave you a list of blocks.
You're able to right click on mobile by holding down, which you can already do for the Data category with variable/list names. It could be explained somewhere, and I'm often concerned about putting the dropdown because of the fact that it can make scripts a lot longer.
Also, you know what I mean by Data category xD
its called variables
ihavenocluewhythisis
Scratcher
500+ posts

Allow changing of how many inputs there are in operator blocks.

ajskateboarder wrote:

TheCreatorOfUnTV wrote:

This idea, allowing changing of how many inputs there are in an operator block, would help users make cleaner code.
Ones that would be affected:
<do logical operation [and v] to <> <> @delInput @addInput :: operators> // Redesign of the boolean blocks.
I feel like the and block could be better worded as:
<<> and <> @delInput @addInput :: operators>
<<> and <> and <> @delInput @addInput :: operators>
-snip-
what if you press the
@delInput
when its only one and? you get
<<> @delInput @addInput :: operators> // clicking the < again deletes the block
oh btw dropdowns could be added, they would be seperate so you can make
<<> [and v] <> [or v] <>@delInput @addInput::operators>

Last edited by ihavenocluewhythisis (Sept. 20, 2024 01:54:57)

GamesReinvented
New Scratcher
100+ posts

Allow changing of how many inputs there are in operator blocks.

ihavenocluewhythisis wrote:

what if you press the
@delInput
when its only one and? you get
<<> @delInput @addInput :: operators> // clicking the < again deletes the block
This could easily be fixed by making it so there can only be a minimum of 2 inputs.
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

ihavenocluewhythisis wrote:

oh btw dropdowns could be added, they would be seperate so you can make
<<> [and v] <> [or v] <>@delInput @addInput::operators>
I like the dropdown idea (and already talked about it), but there shouldn't be multiple dropdowns because it would get confusing.

Last edited by TheCreatorOfUnTV (Sept. 20, 2024 02:25:53)

ihavenocluewhythisis
Scratcher
500+ posts

Allow changing of how many inputs there are in operator blocks.

TheCreatorOfUnTV wrote:

ihavenocluewhythisis wrote:

oh btw dropdowns could be added, they would be seperate so you can make
<<> [and v] <> [or v] <>@delInput @addInput::operators>
I like the dropdown idea (and already talked about it), but there shouldn't be multiple dropdowns because it would get confusing.
how else to make an and or
TheCreatorOfUnTV
Scratcher
1000+ posts

Allow changing of how many inputs there are in operator blocks.

ihavenocluewhythisis wrote:

TheCreatorOfUnTV wrote:

ihavenocluewhythisis wrote:

oh btw dropdowns could be added, they would be seperate so you can make
<<> [and v] <> [or v] <>@delInput @addInput::operators>
I like the dropdown idea (and already talked about it), but there shouldn't be multiple dropdowns because it would get confusing.
how else to make an and or
Just do this:
<[and v] <> <-[or v] <> <> @addInput :: operators>  @addInput :: operators>
It's easier to understand compared to what you wrote.

Last edited by TheCreatorOfUnTV (Sept. 20, 2024 02:37:59)

Powered by DjangoBB