Hello! I was thinking about a feature where you have the option to turn off “cut-offs” in input blocks, it has been here since the new editor update.

How this works: When a Scratcher turns off “Allow cut-offs in input blocks”, input blocks are free from cut-offs. To explain what a cut-off is, a cut-off happens when input blocks have over 50 characters, if it reaches that number, an ellipsis is placed next to the string.

Why I'm suggesting this feature: This kind of feature is convenient, because it would be inconvenient if the Scratcher does not know if there are grammar errors in the input blocks. For example, “The quick brown fox…” is displayed in the input block, while it says: “The quick brown fox jumps over the laz y odg” when the input block is clicked.

Thank you for reading! -NovaShrugs926

Support. This would be useful.

Bump

^^ After the update, blocks with a typable input will now end in a “…” if the input is too long
This gets real annoying when you are writing a lot of information in the say/think block. While it can be convenient for some, it can be more annoying for others

Why not make it toggleable?

OR
have a thing that makes it collapsible and can show the entire thing (If this part is a dupe, let me know, I checked the directory and couldn't find a dupe)


Mockup for this one if the pics don't work
This would make it so you wouldn't have to sideways scroll as much
EDIT: uhh does anyone know how to make the picture smalller? The screenshot was way smaller than it shows on this post.

and its not just those blocks,its every block that you put text in.
Also support, cause this is just an annoying feature

I didn’t even know that that was updated too! Support, since that would be annoying. At this point, I’d recommend that they just revert back to the old version; the new version has caused way too many issues.

I think this is a good idea.

I remember before when it wasn't collapsed, it could go way out of the page, causing some difficulties.

bump

support, it makes it hard to use long strings of text reasonably

bump

BUMP
*encourages you do add some discussion*

Why should it be toggleable? Why would anyone put text in a say or think block if they know it's going to be cut off?

MythosLore wrote:

Why should it be toggleable? Why would anyone put text in a say or think block if they know it's going to be cut off?

Isn't the entire point of the say/think block for text to be said by a sprite?

It doesn't affect how it looks in the project screen

It only affects how the code block looks like

This suggestion would show the entire thing in the CODE or make it collapsible

ChristianScratcher1 wrote:

Isn't the entire point of the say/think block for text to be said by a sprite?

It doesn't affect how it looks in the project screen

It only affects how the code block looks like

This suggestion would show the entire thing in the CODE or make it collapsible

My bad. I thought you were saying that this happened in the speech bubble, not the block. I didn't know this happened with the block.

support

just wondering, what if after a certain length is makes a new line? (won't affect the bubble onstage) (no you cannot make a new line)

I_wantasheep wrote:

support

just wondering, what if after a certain length is makes a new line? (won't affect the bubble onstage) (no you cannot make a new line)

This is sorta in the mockup I made if I'm understanding you correctly
Mockup for this one

ChristianScratcher1 wrote:

I_wantasheep wrote:

support

just wondering, what if after a certain length is makes a new line? (won't affect the bubble onstage) (no you cannot make a new line)

This is sorta in the mockup I made if I'm understanding you correctly
Mockup for this one

yeah it's 101% in the mockup (heckin chonk sized block)

bump

bump

I didn't know they did that, support. I don't want my text to collapse if it is too long. However, I don't want it to be removed entirely.