Instead of asking the user to type in their input, similar to:

ask [] and wait

The user can be prompted to choose from a list, similar to:

ask () and choose from [list v] ::sensing

This is very good because instead of making difficult and laggy drop down menus or making the user type in their choice (which is poor ux, very error-prone, and high friction) it can be done with one, *singular* block

Yes that is all thank you for listening to my presentation

What would the purpose of this block be for?
I assume quiz games,
Semi-support because this might be minimally used

gelatin-free wrote:

What would the purpose of this block be for?
I assume quiz games,
Semi-support because this might be minimally used

Maybe cloud chats (not referring to the ones where you're allowed to type anything because those aren't allowed, but I mean cloud chats with pre-select phrases and emojis)
Also, games where u can click a set number of options or dropdown options

Support, this could clear up confusion for things like quizzes on what you can pick.

Support, that would make questions with a lot of possible answers a lot easier to code without being too confusing

medians wrote:

gelatin-free wrote:

What would the purpose of this block be for?
I assume quiz games,
Semi-support because this might be minimally used

Maybe cloud chats (not referring to the ones where you're allowed to type anything because those aren't allowed, but I mean cloud chats with pre-select phrases and emojis)
Also, games where u can click a set number of options or dropdown options

I support this!

bump

i think, in a way, this already existed with the “Story” extension (found here) scratch had been developing, so i'd like to see it added with an actual list rather than a static 4 items.

bu+mp=welcome to scratch brother

Support!!!

Its easy for kids to understand, and has a good use on Scratch, the 2 main things that projects get denied for, would love to see this added!

HAL95131 wrote:

i think, in a way, this already existed with the “Story” extension (found here) scratch had been developing, so i'd like to see it added with an actual list rather than a static 4 items.

I feel like this should be its own category because face sensing and video aren’t the same

Here is a better version of the block:

ask () and choose from [list v] ::sensing

CSwitch wrote:

Here is a better version of the block:

ask () and choose from [list v] ::sensing

Thanks!

tortoythegod wrote:

HAL95131 wrote:

i think, in a way, this already existed with the “Story” extension (found here) scratch had been developing, so i'd like to see it added with an actual list rather than a static 4 items.

I feel like this should be its own category because face sensing and video aren’t the same

huh? i don't know what you're talking about

Support, the dupe is COMPLICATEDER.

TheOfficialNussia wrote:

Support, the dupe is COMPLICATEDER.

I don't agree, the options being in a dropdown may look simpler, but it would be easier to see what all your options are in the code without needing to open a dropdown, and dropdowns are sorted in code point order, with no way to change the ordering of the items.

CSwitch wrote:

Here is a better version of the block:

ask () and choose from [list v] ::sensing

The list could be a pre-existing list.

//Create a list. Let's say it's name is "Example".
ask () and choose from [Example v] ::sensing

//Or... If we create another list called "List" and the block could look like

ask () and choose from [List v] ::sensing

//or

ask () and choose from [Example v] ::sensing

//if we still have the list named "Example".

I think the block should actually be like this:

ask () and choose from (list v) ::sensing

with the input rounded so you can put a variable in it and change between different lists.

set [list v] to [fruits] // there is a list named fruits
ask [] and choose from (list) ::sensing

support!

this block would be super helpful for prompts and would be easy for new scratchers to understand.

although the workaround:

define ask (prompt) from list
repeat until <[list v] contains (answer) ?>
ask (prompt) and wait
if <not <[list v] contains (answer) ?>> then
ask [invalid answer, try again] and wait
end
end

is pretty simple, we still for some reason don't have round brackets for list blocks so the workaround isn't completely accurate