Buttons werden nicht in der richtigen Reihenfolge in anybutton eingeordnet oder eingefüllt. Mit anderen Worten die Buttons werden nicht in der gleichen Reihenfolge in anybutton eingefügt, oder eingefüllt so wie sie im Designer in der Reihenfolge vorliegen würden oder vorliegen, so dass sie nachher wenn man sie von anybutton wieder abruft, z.b durch "for each item ", so werden sie nachher, wenn man den Text aus der Liste darstellen will, z.b mit oder in einem Label, so kommen die Buttons bzw ihre Texte in einer total chaotischen Reihenfolge heraus.
If you want your buttons to be traversed in a particular order, you must keep their components in a list.
The Every (generic) blocks are best reserved for things like:
- Setting font sizes for all components
- Checking if a component received as a procedure parameter is of a particular type, by checking if it is in lists like Every Label, Every Textbox, Every Button.
The Every blocks make no guarantees as to output order, just completeness.
To bring this in the list is not Problem Bad the order is completly mixed up. For example: wenn i make for buttons with the number button 1 Button du, Button tree, and button for,
Then later it comes out Button one, button four, button twoo and Button 3. And that is not the order what it have in the designer. Why is this simpleting not possible?
It Alters my order.
Here is an example of how to keep button components in order:
For me it is only working backward not chaotically. I tried to put 9 buttons in a list and get back the their order in a list 2 ways. First when screen initialized, second when button pressed. Both order was backward, from last to first. What are you doing with them that calling them chaotically?
I even renamed them without using a list, using only "every button" with "each item" works the same way. Backward.
1 Like
Show us your blocks?
1 Like
Here is the test
I can provide the aia file too.
everybutton_test.aia (3.4 KB)
Test device: Samsung A53 .Android 16.
1 Like
One thing just came in to my mind. Maybe that matters too how are they placed on the screen. I mean it they are in different aligment by vertically and horizontally, put on diffferent layouts in zig-zag way can affect it??? Just an idea. I do not have time to test it today.
1 Like
Yes I agree.
Just an update. I did a quick test with reordered buttons. The result is a bit different.
It handles them in order they were created. So if you delete one in the middle and recrate it again, it will be the last in the line. So the only way to put them in order if you do it yourself as your example.
Hallo osanne, I was testing it by make a new file completly, bei make a new project completly: it every way it was everytime the same problem the any button or every button or any button function or element or how to to name it properly to not course confusion by the explanation to you because in the menu left it names "any button", and the element to use it names "every button", twoo names for the same thing, but you understand what I mean? That's our first problem the developers have no order in name the elements, in one moment they name it any button in the next moment they name it every button this is the first confusion that are in this program, and this can cause bugs .
Okay, now our second problem:
Like I say, I was testing it by move the buttons on the screen when I am in the designer to try if there is a changing in the order what comes out. But no result.
Then I was making a new file:
Where I was make all my buttons in one step, but when I renamed the buttons then it changes, but not in the order where I renamed it, but in the order when I touch it. And I think this is the order what every button or any button takes for put the items inside itself. But in any way there it makes it by a randomly or chaotic way, if not takes it by alpha numeric order, not by order of touching, and not by order of creation. It makes it everytime chaotic. And that is a definitiv a bug, or a error in programming. And this must be solved definitivy.
Because the every button or any button is a wonderful system to make things better, but it not works properly.
And the other problem, and this is definitely a miss programmation, because it is not good for beginners, that's for example the every button element is not compatible with every other elements.
The problem is that the designer and the block Designer are not 100% synchronize it with each other.
And like in the example of any component, there are the naming problem that course confusion for beginners and I am a Beginner.
So the problem is here, sometimes it sort by the order of creation, sometimes it sort it in the order of when you moved it in the designer, but I think it's not sorting it by alpha numeric. In any way it sort it randomly chaotic.
No. It keeps the reverse order they was created in, whatever you do. At least in the real apk file. I do not know about companion I do not use it.
And any button and every button is not the same. The "any button" is like a collective name. It contains a lot of block that can be apllied to "any" element (in our case for buttons) in that group.
The "every button" is only one of the blocks of this group that you can use for manipulating every element (buttons).
And again. It does not change, it keeps the reverse order they were created in. If you move up the last one in the designer it still will be the last, but since you moved up you guess it will be the first. But not.
But maybe I just misunderstand what you are trying to say. Show us your blocks, or aia file so we can see what bothers you.