-
Notifications
You must be signed in to change notification settings - Fork 28
Index In List - Not Working or Doesnt Show #5813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! I tried to reproduce the error you're encountering with a visibility condition using the "index in list" approach, but I wasn't able to find any problems. I set up a page state as a list with a datatype exactly as you described. I've left a video that might help clarify a few things. If you're still having trouble, could you please share a more detailed guide or video showing the exact error? Alternatively, a bug report code from a new blank project would also be really helpful. Best regards |
Hi @Juansarmi , thanks for the reply. I started a new blank project I still have the same problem, restarted my mac still the same, I use flutterflow web, still the same. I watched your video, from 0:26 it seem you also cant get the current index (integer) too? the integer becomes a data type, when the intention is to get the index (integer). Here is what I am trying to do, I have a widget in each row of a list data, which I would like to only show(be visible) if the current index in list is not "0", but I cant do that, when I use conditional If the "integer" becomes "data type" so I cannot compare it with an integer. I am very positive I can do this previously, because on my current project I depend on it, it still currently works but If I make changes to it then it wont work, it seems theres an update or some sort? code expression is also now called Inline functions it seems. The only work around to this is I create a new field called "index" and generate list of index myself for the list of data, but that would be very time consuming for my whole project. This is a screenshot of my intention, this was made before the bug I have. As you can observe, it uses a conditional If If Index In List Not Equal To **Inline Function (var1 - 1, var1 = Index In list) ** ![]() So basically I can click "Index In List" then it will show as Integer, but when I click confirm it becomes a data type. Here is a video starting from blank project then I tested using code expression (inline functions) works, but when using conditial if theres an issue. Bug Report Code |
Hi again! Thanks for providing all this additional information. Unfortunately, I haven’t been able to view the videos due to lack of permissions. Anyway, I’ve been able to confirm that there’s unexpected behavior with the "index in list". I’ll be sending this over to the engineering team for further investigation, and I’ll bring you updates as soon as I have them. Best regards. |
I found a work around if updating an app or page state. You can map the field to update first and then it will take the Item In List option. But not like before where you had a dropdown with: Item in List, Database Structure or To JSON |
Same problem here! To get around this, I now need to pass the list index through a Code Expression (Now Inline Function). |
I found a hack/ work around. So it seems if you want to use the index in list as a function argument custom or inline, when hitting confirm it will store as the list item map. i found if you select list index and then copy it will exit and remain as list index lol. |
Can we access your project?
Current Behavior
Whenever trying to select Index In List in a listview component it doesnt work.
Expected Behavior
I should be able to select / get the index of a list view
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT5ThvHqy5dNrsRE7ZCBb8J7/SQsJmY6RYI3itYbVUkaDOvvOpkiffTBdXFJXMu4d2xUJGH8sGAIpvfHkvzXFMArG0iIQ70/z6tQZALyQnmuSoyuCpCCVEZtGdpMGkyX4JqOih5/Ju1eWGdm7HGEeu/ITgDcNYTrPmwvPOa1OtvI+UKdK3rBDzhmtmNecCfn
Visual documentation
Environment
Additional Information
No response
The text was updated successfully, but these errors were encountered: