-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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
FlexibleSpaceBar collapse or expanded event #18567
Comments
I think this SliverAppBar component needs more love. For the title widget it says it is the primary content when expanded. But if I add paddings etc. and when it collapses it still uses the same widgets and it goes out of the screen. And also for the long titles, the text goes out of screen and not wraps properly. |
Does anyone has a workaround suggestion for this ? |
Also different background colors for expanded and collapsed states, maybe? |
Anything on it yet? Still need something to tell if the flexibleSpaceBar is collapsed or expanded |
Since the flexibleSpace parameter of the SliverAppBar could take any widget. |
Hi @visualsanity |
Without additional information, we are unfortunately not sure how to resolve this issue. Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
I have looked through the documentation for the SliverAppBar / FlexibleSpaceBar widgets for a callback, a state or event to hook into, when the FlexibleSpaceBar is collapse or expanded fully. I haven't been able to find anything.
What I'm looking for is the ability to change the title field when in a different state.
Am I looking in the right area of the documentation?
https://stackoverflow.com/questions/50909791/flutter-change-text-when-flexiblespacebar-is-collapsed
The text was updated successfully, but these errors were encountered: