You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Blockly, there's an unused field type that Scratch didn't work with called FieldTextDropdown that is reminiscent of the text dropdown fields from Scratch 2.0
It's possible to reimplement them into an extension (which is how I got the image), but not without ScratchBlocks being defined and a lot of goofy code, so it's no where near ideal or as resilient as it actually being incorporated.
It would be extremely useful if these were reimplemented, as I can think of countless examples where I would use this, including extensions I'm currently working on. One way I could imagine this being implemented is having a parameter alongside menus for "acceptStringInputs" that could be enabled if "acceptReporters" is also true.
The text was updated successfully, but these errors were encountered:
In Blockly, there's an unused field type that Scratch didn't work with called FieldTextDropdown that is reminiscent of the text dropdown fields from Scratch 2.0
It's possible to reimplement them into an extension (which is how I got the image), but not without ScratchBlocks being defined and a lot of goofy code, so it's no where near ideal or as resilient as it actually being incorporated.
It would be extremely useful if these were reimplemented, as I can think of countless examples where I would use this, including extensions I'm currently working on. One way I could imagine this being implemented is having a parameter alongside menus for "acceptStringInputs" that could be enabled if "acceptReporters" is also true.
The text was updated successfully, but these errors were encountered: