but you cant create a button list with a block that create 1 to 36 in one block?. for not create button for button in the list?. and call a number block using any component.
We could really do with an every componentName block as well
100% agree with this comment. I addition to (or in place of) "componentName", I'd like to see every MIT App Inventor component have a String "tag" which could be set differently from the "componentName". Visual Basic, for example, allows components to be "tagged" differently from their name, which helps a lot when there are many of the same component and/or you want the tag to be different from, or simpler than the component name.
It would really help if you provided a screenshot of your relevant blocks, so we can see what you are trying to do, and where the problem may be.
To get an image of your blocks, right click in the Blocks Editor and select "Download Blocks as Image". You might want to use an image editor to crop etc. if required. Then post it here in the community.
Yes, my Problem was that the green "every button" block don't work directly if it is putted in the place from the orange "get button" block, this might bi a bug to solve in the future or it is an idea to make the code shorter or more direkt, might this bi an idea for the developers?
Actually, the nb193 release included a number of list related operators that one would typically find in a functional programming language (App Inventor actually targets Scheme under the hood). However, there's a bit of finagling to be done because App Inventor forces blocks to either return values or not, whereas in Scheme technically every S-expression returns a value. You can use the map operator to apply an operation to every object: