Currently, editing custom blocks (not their definitions) and adding boolean/string inputs to them only adds them to the end. It is a hassle to remove all the ones after where you want to insert the new input and retype them again. I am suggesting the ability to insert an input anywhere in the block. This can be done by going to an argument in a custom block, and when clicking any of the 3 options, it is added after the selected part of the custom block.



Another option is for it to work similar to Snap! where there are plus signs between and around inputs and labels in custom blocks that you can click to add new ones.

Advantages:

• Easier to edit custom blocks, and makes more sense.
  
• Less likely to make mistakes when re-adding arguments and break large custom blocks.
  

Disadvantages:
None that I can think of.

Hmm good idea!, I think programming from scratch would be much easier with your idea.

I’ll ask a moderator to move this over to the Bugs and Glitches forum - it seems like more of a fit for this topic. Sometimes, people might say “reported to be moved” - this is not bad like on the main site - the forums have a different report system and it’s really no different than sending a text message to a Scratch Team member.

Let me know if you have any questions.

Thanks! :)

Umm, you already can. Reporting this to be closed.

AlfabetonsOfficial wrote:

Umm, you already can. Reporting this to be closed.

No, you can't.

Bump

Support!, I've had to delete all the inputs in front of where I want to insert something and add them back after which is a big hassle.

removed - misread the OP

mrcreatorluigi wrote:

Support! Now you don’t need to have wide blocks in the middle, instead making them small.

But I have a small problem. You could have a bunch of these scripts, however it would be confusing in the block grabber section (whatever you call it) in which you pick the scripts blind and don’t know what they do. This was probably intentional to avoid making them confusing.

I don’t know if I read the OP correctly so beware with me

It is about editing custom blocks (not their definitions) and removing the need to delete all the inputs in front of where you want to insert a new input

Bump

You can already do this, next to input and boolean there is a “text” option, reporting to be closed as implemented

And don’t you dare say it doesn’t relate, it does, it will look like this:

Text (input) <boolean::operators> text::custom

There, now it’s in the middle

Pianostar4 wrote:

You can already do this, next to input and boolean there is a “text” option, reporting to be closed as implemented

And don’t you dare say it doesn’t relate, it does, it will look like this:

Text (input) <boolean::operators> text::custom

There, now it’s in the middle

You probably misread the OP.

Currently, you can only add a boolean or string input at the end of a custom block while you are making it. The OP is suggesting the ability to add a boolean or string input anywhere in the block.

Reev0102 wrote:

Pianostar4 wrote:

You can already do this, next to input and boolean there is a “text” option, reporting to be closed as implemented

And don’t you dare say it doesn’t relate, it does, it will look like this:

Text (input) <boolean::operators> text::custom

There, now it’s in the middle

You probably misread the OP.

Currently, you can only add a boolean or string input at the end of a custom block while you are making it. The OP is suggesting the ability to add a boolean or string input anywhere in the block.

Still, it isn’t that hard to erase one or two things. Who makes 10 input long things lol
(Sorry if I sound harsh, it’s just my viewpoint)

Support! I sometimes click on the wrong button, and I often use custom blocks with multiple inputs.

Still, it isn’t that hard to erase one or two things. Who makes 10 input long custom blocks?

Griffpatch.

Pianostar4 wrote:

Reev0102 wrote:

–snip–

Who makes 10 input long things lol

I do.

JJ09012011 wrote:

Still, it isn’t that hard to erase one or two things. Who makes 10 input long custom blocks?

Griffpatch.

Lots of people do. It isn't only about how many inputs there are in the custom block though, but that you also need to remember the names to these inputs you removed then re-added and replace all of the ones that were in the custom block definition.

Pianostar4 wrote:

Reev0102 wrote:

Pianostar4 wrote:

You can already do this, next to input and boolean there is a “text” option, reporting to be closed as implemented

And don’t you dare say it doesn’t relate, it does, it will look like this:

Text (input) <boolean::operators> text::custom

There, now it’s in the middle

You probably misread the OP.

Currently, you can only add a boolean or string input at the end of a custom block while you are making it. The OP is suggesting the ability to add a boolean or string input anywhere in the block.

Still, it isn’t that hard to erase one or two things. Who makes 10 input long things lol
(Sorry if I sound harsh, it’s just my viewpoint)

2D / 3D rendering can get quite complicated sometimes

hehe

Bump