TurboWarp
Better Input Extension
VERSION 4.0!!
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Doesn’t really matter. If there’s no response it will return empty; just like the current ask and wait block
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Doesn’t really matter. If there’s no response it will return empty; just like the current ask and wait block
It does matter, actually. For parity with the actual ask block, you should return an empty string.
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Doesn’t really matter. If there’s no response it will return empty; just like the current ask and wait block
It does matter, actually. For parity with the actual ask block, you should return an empty string.
No that’s what I mean, it will return an empty string when there’s no input
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Doesn’t really matter. If there’s no response it will return empty; just like the current ask and wait block
It does matter, actually. For parity with the actual ask block, you should return an empty string.
No that’s what I mean, it will return an empty string when there’s no input
It should also do that when it's cancelled. Make a boolean that is toggled when an input is cancelled or not.
Adds various blocks for custom CSS inputs. Focused on remodeling the ask () block to be better.
Should UserInput return null instead of 'canceled' without input?
Doesn’t really matter. If there’s no response it will return empty; just like the current ask and wait block
It does matter, actually. For parity with the actual ask block, you should return an empty string.
No that’s what I mean, it will return an empty string when there’s no input
It should also do that when it's cancelled. Make a boolean that is toggled when an input is cancelled or not.
I might add the Boolean for that in a later update. I like the cancel button the way it is thought since the button makes the input report cancelled. That way people can use better input as a button selection thing rather than an input and press OK. That’s also why the Input and cancel button has an option to be enabled or disabled.
Extension was updated. Merged some blocks, changed some names and functions, added the ability to enable/disable 2 more buttons and fixed some bugs.
Hey sharkpool? Can you possibly make it so you can force-submit the input? This would be handy for having the "enter" key be another option to submit your inputs.
Hey sharkpool? Can you possibly make it so you can force-submit the input? This would be handy for having the "enter" key be another option to submit your inputs.
its ask and wait which means it should wait, and force submitting the input without the users permission could be annoying due to it having the off chance to force submit a unfinished sentence word, or anything that was typed, i say this because it could be multi-line. if possible it should just be "shift-enter" to submit, or like in the console set it to "enter" and to add a new line set it to "shift-enter"
That's a good suggestion. Maybe also, Shift enter could create a new line and enter could submit it. It will act as the submit button, but not a replacement of it.
That's a good suggestion. Maybe also, Shift enter could create a new line and enter could submit it. It will act as the submit button, but not a replacement of it.
Hi, so I read the past couple comments. I’ll consider the shift enter thing. I’ll either add it or add a block that allows/doesn’t allow enter to submit.
Thanks so much! This beats the ask and wait block in every possible way now, I won't have to use that block anymore.
Thanks so much! This beats the ask and wait block in every possible way now, I won't have to use that block anymore.
Thanks :)
Thanks so much! This beats the ask and wait block in every possible way now, I won't have to use that block anymore.
Updated! Added that block and some more 👀
Thanks so much! This beats the ask and wait block in every possible way now, I won't have to use that block anymore.
Thanks!!! Updates coming soon :)))
3.0 is RELEASED!!!
In this Update: -Bug Fixes -Infinite Buttons -Image Setting for More Elements -ALL Elements update live -Vertical Sliders -Updated Palette
How do I change the background colour in the extension ask ui
set textbox color block
I have a suggestion, you should make it so we can have more than one input typing thing
I have a suggestion, you should make it so we can have more than one input typing thing
With the way I built the extension, no. As a alternative just make multiple boxes
marking as draft as im rewriting this from scratch. This will be closed after