We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/xuelongqy/flutter_easyrefresh/blob/v2/example/lib/page/sample/nested_scroll_view.dart 在上面这个页面的flexibleSpace中我加了一个搜索按钮,并通过control调用callRefresh方法,发现flexibleSpace会先折叠起来再展开然后再显示更新的header,有什么办法能直接显示header而不是先折叠再展开吗? flexibleSpace: SingleChildScrollView( physics: NeverScrollableScrollPhysics(), child: Container( padding: EdgeInsets.only(top: 80), child: RaisedButton(onPressed: (){ _refreshController.callRefresh(); },child: Text('刷新'),), ), ),
flexibleSpace: SingleChildScrollView( physics: NeverScrollableScrollPhysics(), child: Container( padding: EdgeInsets.only(top: 80), child: RaisedButton(onPressed: (){ _refreshController.callRefresh(); },child: Text('刷新'),), ), ),
The text was updated successfully, but these errors were encountered:
这是Flutter列表的设计,以及EasyRefresh的原理是超出顶部才能刷新。所以是必然现象
Sorry, something went wrong.
peng8350/flutter_pulltorefresh#270
这里修正了 与easyRefresh 现象一样 @xuelongqy
peng8350/flutter_pulltorefresh#270 这里修正了 与easyRefresh 现象一样 @xuelongqy
感谢提醒,已修复,将会在下个版本发布
修复:NestedScrollView中调用callRefresh出现折叠 [issues#172](#172)
4e69dfc
No branches or pull requests
https://github.com/xuelongqy/flutter_easyrefresh/blob/v2/example/lib/page/sample/nested_scroll_view.dart
在上面这个页面的flexibleSpace中我加了一个搜索按钮,并通过control调用callRefresh方法,发现flexibleSpace会先折叠起来再展开然后再显示更新的header,有什么办法能直接显示header而不是先折叠再展开吗?
flexibleSpace: SingleChildScrollView( physics: NeverScrollableScrollPhysics(), child: Container( padding: EdgeInsets.only(top: 80), child: RaisedButton(onPressed: (){ _refreshController.callRefresh(); },child: Text('刷新'),), ), ),
The text was updated successfully, but these errors were encountered: