YES! I've always wanted that!
Using this, I made this
For some reason, it wont let you use blocks in dropdowns, so I had to use that
O think it would look nicer if you showed the Lisp notation instead of the xml. Other than that, that's a cool demonstration!
i have no clue what lisp notation is
huh, interesting. is there a way to do this with just the extension [ V] [] @addInput::other block?
I don't think so, but you can use ([text V] of (split ((block)@addInput::ring) by [blocks v]))
kk
The code to blocks to code library, which that block is from, doesn't even use any extension blocks. I personally would recommend using the library, as it makes it a lot clearer what you're actually doing.
I'm going to use this to make a cool dictionary library that actually populates the dropdown with the correct keys!
Should these posts be moved to a new topic, since we've been talking about a completely different topic than what this thread was originally about (plus, having a topic about dynamic dropdown menus would be much better)?
absolutely
but what about the block definition? wouldnt this mean there would be ringified hat blocks and multiple scripts reported from the definition block?
you have to do menu>scripted instead of options
edit: oh i see it now
in the same menu with the options thing?
but how do I add a menu item
edit: oh nvm snap froze but it was actually always working
I told Jens that someone would ask for this! :~)
please, Jens 
(why is snap bugging)