Incorrect Order of every(component v) Block

Bugs and Other Issues
,
1

When using the every() block, which is available in the Any component, to create a list of 11 buttons on the screen, the buttons are inserted in order from Button 1 to Button 11. However, when using the every() block to create a list of 11 player components, the order becomes 10, 11, 1, 2, 3, ... 8, 9, and so on, with 2-digit numbered components appearing first. Since the order remains the same even after changing the component names, it seems to be based on the order of creation. Similarly, even for player components, using the every() block should correctly arrange numbers 1 to 11 in the list order. Please fix this so that player components, just like buttons, are sorted correctly using the every() block.

image
image532×1125 46 KB

test2.aia (186.8 KB)

2

This issue has been raised by Power Users before with MIT developers.

They have tried @ 5 different approaches to this over the years, none of which have yet made it to release.

The workaround is to create a second list of all the component names, in the same order as the every component list.

3

Search this board for Wordle In A Day to see how quickly you can build a component list manually.

4

This is not a bug. No where do we claim that the every component block sorts components by name. In fact, it can't easily do that because components do not have knowledge of their names so they cannot be sorted by them.