Basically I have columns and within those columns are buttons. So for example column 1 will have button 2 and when you press column 1 button 2 column 1 will go invisible and column 2 button 3 will be visible. It works for first column button 97 button 110 and button 111 are buttons to working column but when I tap on other columns the column collapses why is that I tried to check my block over and over and they seem fine to me is it a bug or am I doing something wrong
If your column height and width is set to âfit contentâ and the only content is a button that is not made visible, or that there isnât any content at all, then the column would shrink to nothing.
By the way, have mercy on usâŠ
You know that computers can do a screen capture? That would be a lot easier on the eye than taking of photograph of a monitor.
Also, naming every component using the default name makes the intention very muddled; to say nothing about the fact that you organize them randomly. The Button115 logic is at top left, 97 at bottom right, but 117 is dead center⊠come one, mind keeping it a bit more tidy?
1 Like
It canât be height width or any other because when I made the first one I duplicated to create the rest
And I used to post computer screenshots but the results werenât much different unless I zoomed and I had to take several
And I meant 97-110- and 111* not 1117. All of them are in ascending order with 97 closing first column and showing second. 110 closing first and second and showing third and so on
I donât understand too well what you are trying to do but the way you make those blocks it seems like you are ignoring the âprocedures, variables and clone componentsâ that would make that a lot of simplier and less blocks ass well , maybe read the docs about how you can use procedures and variables and if still you donât find a solution comeback and tell us what you did not understand and I can help you
Iâll try to rename columns and buttons so you can understand better
1 Like
Trust me: all that moiré effect that shows on photographs would not appear on a screen capture. And the colour would appear even. And the smudge and dirt on your screen would not show.
2 Likes
Renaming columns did not fixed the issue
The renaming was not meant to help fix the problem, but ease in isolating it.
So, basically, the ones that are working are ONLY those labelled âuser 1â.
Can you show screen capture of the interface?
With various stages of columns visible (as apparently, you set it such that clicking the button in column1 makes that column become not visible, while column2 becomes visible, with each button click moving the visibility âdeeperâ) so that the expected behavior is illustrated.
Where are the various âuserâ column located?
learn how to work with âprocedures, variables and clone componentsâ and trust me it will be better , since no one can exactly understand what your app is going to be and youâll be able to make a greater and potential app! 
Yes definitely but right now I want fix to this problem only this is the only issue in my app
Where are the buttons?
And what is this?
(That was mighty hard to capture, since it flashes on and off).
That said, the way your columns are organized, your âuser 2 column 1â is the PARENT of âUser 2 column 2â. So if your button 1 makes column1 not visible, ALL its children (column2, column3, column4) will also be forced to be invisible, because their ecosystem column1 is invisible.
I think that this is where you have your problem.
1 Like
Right now they are in one column and in that column I have user 1-4 columns should I put them in different columns or separate columns
Can you pm me I would share my app link with you and then you can tell me whatâs wrong
I am somewhat busy these days and would not be able to grant as much time helping people as I did recently; so, sorry about that.
As to what you should do with your columns, that is a completely different issue. You got @Daniel_Coglitore advising you on a better way to approach the app from an operational point of view, but you insisted that you only wanted to make your present approach to work. Why the change of heart?
Your whole approach to have hundred of columns and hundred of buttons (judging by the original default naming which I presume was purely sequential) whichâs only purpose is to make other columns visible and making their own parent column invisible is flawed as being overly specific and wasteful of resources. Good programming is about making parts of the code reused, not as duplication, but as instantiations with new arguments. With those clones, you have everything loaded statically in as many objects as you have data, and have a complex scheme to just show one at a time, when you should show the same objects displayed all the time, but simply reloaded with different data each time.
You are in the situation where you need to take a different fork each time you want to eat a different bite.
Conceptually, you have to start over, from scratch.
2 Likes