You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really an issue, looking for a way to have a searchable list with a regular ListView instead of ListView.builder.
I have a table with a lot of sparse fields, the searchable list makes it easier, but because there are so many fields the ListView.builder loads them as you scroll and if you save before scrolling to the end then it doesn't pass all the values.
I pulled out the searchable_listview and search_text_field code into my repo, the change to do this as a ListView is inside the renderListView method
The widget.builder! was an issue for the list view. Seems like any builder methods will lazy load.
I'm not sure how the change would fit in with your repo, but this would be a nice option to have in your package if possible. 👍
The text was updated successfully, but these errors were encountered:
@letto4135 thanks for your feedback and sending me your suggestion for this
It can be achieved if we add a parameter lazyLoading that will indicate if the searchable listview will use Listview.builder or just Listview simple constructor.
if I had other solution I will let you know, otherwise I'll let you know once published on pub.dev
Hello there.
Not really an issue, looking for a way to have a searchable list with a regular ListView instead of ListView.builder.
I have a table with a lot of sparse fields, the searchable list makes it easier, but because there are so many fields the ListView.builder loads them as you scroll and if you save before scrolling to the end then it doesn't pass all the values.
I pulled out the searchable_listview and search_text_field code into my repo, the change to do this as a ListView is inside the renderListView method
The widget.builder! was an issue for the list view. Seems like any builder methods will lazy load.
I'm not sure how the change would fit in with your repo, but this would be a nice option to have in your package if possible. 👍
The text was updated successfully, but these errors were encountered: