Don't worry, don't want you to have to solve all of my issues, just wanted to know what was expeted behaviour. I'll take a closer look and if I still can't turn anything up or I find something relevant to the library I'll report back
(might be a while though)
help... I'm in agony...
I'm try to using dynamic TabBar based on response from my API server , i got two tabs every tabs i'm using on it your inifinte_scroll plugin .. I have used controller refresh method , but i got two tabs with same List items
Container(
child: FutureBuilder<List<Category>>(
future: _con.getRestaurantFoodsCategories(),
builder: (c, s) {
if (s.hasData) {
List<Tab> tabs = new List<Tab>();
for (int i = 0; i < s.data.length; i++) {
tabs.add(Tab(
child: Text(
s.data[i].name,
style:
TextStyle(color: Colors.black),
),
));
}
TabController tabController =
new TabController(
vsync: this, length: tabs.length);
tabController.addListener(() {
updateSearchTerm(
s.data[tabController.index].id);
});
return Container(
height: 500,
child: new MaterialApp(
debugShowCheckedModeBanner: false,
home: new Scaffold(
appBar: new AppBar(
backgroundColor: Theme.of(
context)
.scaffoldBackgroundColor,
title: Padding(
padding: const EdgeInsets
.symmetric(
horizontal: 20),
child: ListTile(
dense: true,
contentPadding:
EdgeInsets.symmetric(
vertical: 0),
leading: Icon(
Icons.restaurant,
color: Theme.of(context)
.hintColor,
),
title: Text(
S
.of(context)
.food_categories,
style: Theme.of(context)
.textTheme
.display1,
),
),
),
bottom: new TabBar(
controller: tabController,
labelColor: Colors.black,
isScrollable: true,
tabs: List<Widget>.generate(
s.data.length,
(int index) {
updateSearchTerm(int searchTerm) {
_con.idOfCategory = searchTerm;
_con.pagingFoodsController.refresh();
print(searchTerm);
}
_con.idOfCategory = searchTerm;
_con.pagingFoodsController.refresh();
print(searchTerm);
}
here is my videos shows my app problem
i hope this clear to u
Hi @EdsonBueno man thanks for this beautiful library it helps a lot. There is one thing that I am not able to figure listed in this issue [Github]flutter/flutter#42159 .
Any suggestion to fix this behavior
Any suggestion to fix this behavior
@EdsonBueno sorry was away for a while, yeah nothing from the suggested works but what i did is cached all the children of listview that are lazily loading through pagination. Means at some point we will have a heap/memory overflow but we are going for this, until flutter fixes that one or we can fix it in some other way
_pagingController.addPageRequestListener((pageKey) {
print("Listener Added");
});
I have added same Listener at multiple screens but with some screens its not working even its not adding PageReqesutListener .
Whats the solution ??
When I use the "noItemsFoundIndicatorBuilder," it has intrinsic height of the entire screen. I want it to have 0 height and have tried building a widget with 0 height. However, it still somehow has full height. Is there any way to show a Container with 0 height that doesn't expand to fill the entire space for the indicator builder?
Here's my code:
CustomScrollView(
controller: widget.scrollController,
reverse: true,
slivers: [
PagedSliverList(
pagingController:
context.read<MessagePagination>().pagingController,
builderDelegate: PagedChildBuilderDelegate<ChatMessage>(
firstPageProgressIndicatorBuilder: () =>
CustomLoadingSkeleton(type: "image-skeleton"),
newPageProgressIndicatorBuilder: () =>
CustomLoadingSkeleton(type: "image-skeleton"),
noItemsFoundIndicatorBuilder: (_) => Container(
constraints: BoxConstraints.tight(Size(0, 0)),
padding: EdgeInsets.all(0),
color: Colors.purple,
height: 0,
width: 0,
),
itemBuilder: (context, item, index) {
controller: widget.scrollController,
reverse: true,
slivers: [
PagedSliverList(
pagingController:
context.read<MessagePagination>().pagingController,
builderDelegate: PagedChildBuilderDelegate<ChatMessage>(
firstPageProgressIndicatorBuilder: () =>
CustomLoadingSkeleton(type: "image-skeleton"),
newPageProgressIndicatorBuilder: () =>
CustomLoadingSkeleton(type: "image-skeleton"),
noItemsFoundIndicatorBuilder: (_) => Container(
constraints: BoxConstraints.tight(Size(0, 0)),
padding: EdgeInsets.all(0),
color: Colors.purple,
height: 0,
width: 0,
),
itemBuilder: (context, item, index) {
@EdsonBueno Please don't make assumptions.
AutomaticKeepAliveClientMixin works but it's suboptimal. The issue of AutomaticKeepAliveClientMixin is that it keeps widget in the memory, causing uncessary resource cost when there is a large number of items. ListView with PageStorageKey does not need to keep all the items alive.
Hi @EdsonBueno had a doubt regarding the pagination functionality when there are only few items to be displayed (the total count of items is only 3 which is why I am considering the first API call itself to have the last set of items ). My issue is very similar to EdsonBueno/infinite_scroll_pagination#30 where in there are two network calls taking place even though I am using the appendLastPage() function. Was wondering if there is something I am missing here
thanks!
thanks!
i need some help please as i've been trying to make this work for more than 2 hours now but no luck at all
Jim @enchance Oct 05 23:42
I tried limiting it to 2/page +
I tried limiting it to 2/page +
Future.delayed(Duration(seconds: 2)) just to see what would happen and it starts loading each next page every 2 seconds as expected until all 14 is loaded. This is all once the screen is opened w/o having to scroll to the bottom. Any suggestions? I can post the code on github if you need.