Thanks a lot man. I had been looking for an efficient way to do this. I saw the IndexedStack approach online and didn't care for it much. The 3rd approach is the way mehn. Thanks once again.
Skip to 9.50 for the ability to retain navigation state between tabs. (I had a map view which modally presents a page and needed that page to remain when changing tabs).
You provided an excellent comparison between IndexedStack, PageStorage, and AutomaticKeepAliveClientMixin. How effective is AutomaticKeepAliveClientMixin compared to PageStorage for large projects since AutomaticKeepAliveClientMixin keeps those widgets in memory?
Thanks for asking. I go for AutomaticKeepAliveClientMixin based on its simplicity and less boilerplate code as i mentioned in the video. I'll have to confirm this but i believe the PageView uses the PageStorage behind the scene to store the scroll offset but it doesn't work here since we're triggering a setState which rebuilds the PageView. Plus we also have to maintain the state so that's why using AutomaticKeepAliveClientMixin works better here. I haven't done any performance test to compare the two approaches. Every approach has its pros and cons and your use-case would differ so choose the one that works best for you :)
Beautiful tutorial. Quick Question: (Using the 3rd Option) If i am on the counter (Home) page and i hit a button that navigates me to another page (Lets call it question page) . If i navigate to the trending page and navigate back to the Home page , will i still be on the Questions Page ?
Welcome to the channel. Thanks for the compliment. Try it out and give us your feedback. We get our hands dirty with codes here. #SoroSokeGeneration Thanks.
This was really helpful, the third method is just what I needed. Thanks
Nwanne you're welcome.
7:42 Third and best method
Good choice.
Thanks a lot man. I had been looking for an efficient way to do this. I saw the IndexedStack approach online and didn't care for it much. The 3rd approach is the way mehn.
Thanks once again.
No yawa.
I'm glad you found it useful.
Superb video, clear and concise, provides a few options and their pros and cons, and is of course helpful. Love it! Thanks so much!
Glad it was helpful!
Thanks, the 3rd approach works for me !! 7:44
Nice :-)
such a great explanation of the implementation and the scheme !
Awesome explanation thank you man 🤝🏻
Thanks Emmanuel you save our time.. Thanks again
Skip to 9.50 for the ability to retain navigation state between tabs. (I had a map view which modally presents a page and needed that page to remain when changing tabs).
Really great video buddy, you break it down really well. 👌
Glad you liked it!
Very practical tutorial..Thanks
Glad you liked it.
Thanks I've been looking for this
Glad I could help
me encanto, me sirvió de mucho, I love it, it helped me a lot
Good to see a new video from you
Yeah...I would try to upload new stuffs weekly from now on.
Is there any topic you'll like to see or any concept you find difficult?
@@fleepgeek It would be great to get a series where you build a complete functional flutter app with state management from scratch to completion.
Thank you for this man, really helped.
You're welcome.
This was awesome, thank you so much!! 👏👏
You're welcome
You provided an excellent comparison between IndexedStack, PageStorage, and AutomaticKeepAliveClientMixin. How effective is AutomaticKeepAliveClientMixin compared to PageStorage for large projects since AutomaticKeepAliveClientMixin keeps those widgets in memory?
Thanks for asking.
I go for AutomaticKeepAliveClientMixin based on its simplicity and less boilerplate code as i mentioned in the video.
I'll have to confirm this but i believe the PageView uses the PageStorage behind the scene to store the scroll offset but it doesn't work here since we're triggering a setState which rebuilds the PageView.
Plus we also have to maintain the state so that's why using AutomaticKeepAliveClientMixin works better here.
I haven't done any performance test to compare the two approaches.
Every approach has its pros and cons and your use-case would differ so choose the one that works best for you :)
Simply Awesome !!
Thanks a lot!
Hi when we need nested navigation, so i case i develop Ecommerce for web and bobile?
You absolute legend.
Thanks.
I'm glad you found it helpful.
I want to give you 1000 👍Like. Thank
Subscribing would be just enough ;)
You're welcome
Beautiful tutorial. Quick Question: (Using the 3rd Option) If i am on the counter (Home) page and i hit a button that navigates me to another page (Lets call it question page) . If i navigate to the trending page and navigate back to the Home page , will i still be on the Questions Page ?
Welcome to the channel.
Thanks for the compliment.
Try it out and give us your feedback.
We get our hands dirty with codes here.
#SoroSokeGeneration
Thanks.
Thanks man
You're welcome!
Does keep alive mixin work with stateless class as well?
A simple Google search would give you this answer faster than my reply.
Thank you!!!
Thank you for great work.. Pls see => AutomaticKeepAliveClientMixin method is not working..
What exactly is not working?
Try downloading my code from GitHub and try it out.
You might be missing something.
PageView() gotta be the best option
Glad you found the one that works for you :-)
super.build(context) is giving me error.
What error?
@@fleepgeek Thanks it was my bad .. I figure out to correct it and it worked
THANKS :'D
You're welcome.
tq
💪
dude, just use state management if u dont want to lose a state of that variable
Okay dude.