Awesome! Guess now I got what's going on under the hood of all these state management solutions. Although I keep going with one of them for simplicity reasons. Anyway, great explanation! Highly appreciated your contents. Keep goin and merry Xmas!
Thanks! Merry Christmas 🎄 Yep totally fine to use Riverpod, Provider, etc. 👍 Riverpod State Management Tutorial: th-cam.com/video/8H3bwxxla4Y/w-d-xo.html Provider State Management Tutorial: th-cam.com/video/kN9Yfd4fu04/w-d-xo.html
First of all thank you for this content bro here is question 06:30 when i add final String name; as varaiable on dependonMyinheritedWigetExactype() will i also change it to dependonMyinheritedWigetExactype().name ? 💁♀
Instead of putting a StatefulWidget on top of the InheritedWidget, couldn't you have just extracted the counter into a separate class with an increment method?
Very well explained. Thanks! As a newcomer I have to say - clearly Flutter has big problem with state management. I know there are 3rd party packages, but c'mon.. there should be a better, clean way.
As far as I can tell, we are storing the state inside the InheritedWidget twice. Once from the Stateful widget, and one inside the InheritedWidget itself. The only time we use the state inside the InheritedWidget, is when we check between current and previous state inside updateShouldNotify. So what we do is keep two states in sync. When the stateful widget updates, it creates a new InheritedWidget which will trigger an updateshouldNotify, which will trigger a UI update. Is that correct?
Thank You @KostasOreopoulos! Follow this link: semaphoreci.com/blog/state-management-flutter-inheritedwidget-provider-state-management#:~:text=InheritedWidget%20is%20a%20tool%20for,the%20use%20of%20the%20context. I hope you will get your answer 🙂
Most ppl nowadays are visual learners. So was wondering why they do not have the views and constrains tabs for Flutter development like in Java/Kotlin for Android Studio. They are very confusing building apps in the style of React when u have too many views.
Thank you for the good video. As a note: so if I am correct, a drawback of InheritedWidget is, if your InheritedWidget is not above your MaterialApp and you push a page, then the children widgets will not be able to access the state variables of the InheritedWidget anymore. But if you put it above the MaterialApp then all ancestors and children will be able to access the state variables in the InheritedWidget. So how does one go about fixing the problem when a page is pushed and the InheritedWidget's state becomes inaccessible, because I am guessing this is due to the Navigator?
Thank You J Richards! Follow this link: medium.flutterdevs.com/inherited-widget-in-flutter-604b0f009297#:~:text=In%20flutter%2C%20the%20inherited%20widget,references%20when%20a%20change%20occurs. I hope you will get your answer 🙂
@@HeyFlutter I actually agree with that logic. I too believe first learn to code those basics.. Then pick up on packages, lib.. Etc etc.. Hey by the way wrote you a email.. Hope you were able to read it.
Most state managements make use of the InheritedWidget, also the Provider. The Provider is only wrapping the InheritedWidget and has some more features for more comfortable usage. Therefore it is always good to learn the basics of the InheritedWidget because it is used almost everywhere under the hood.
This might help you :)
👉 12 Week Flutter Training from Newbie to Expert: heyflutter.com
Source Code: github.com/JohannesMilke/inherited_widget_example
BuildContext Tutorial: th-cam.com/video/ALmd6jLqUK8/w-d-xo.html
Riverpod State Management Tutorial: th-cam.com/video/8H3bwxxla4Y/w-d-xo.html
Provider State Management Tutorial: th-cam.com/video/kN9Yfd4fu04/w-d-xo.html
Riverpod Calculator Tutorial: th-cam.com/video/6isW26d9TiE/w-d-xo.html
Tinder App Tutorial: th-cam.com/video/v1wofhoutBk/w-d-xo.html
Shop UI Tutorial: th-cam.com/video/CQZr-GXe__Y/w-d-xo.html
Todo App Tutorial: th-cam.com/video/kN9Yfd4fu04/w-d-xo.html
Any doubt in flutter, you can count on this guy.
Thank You
Thanks, for your support, @user-im9wp8eo9s! 🙂
I've been struggling to find an in-depth approach of inherited widget for days. Thank you so much for this video, awesome job!
You are welcome, Willian Chimura 😊
Awesome! Guess now I got what's going on under the hood of all these state management solutions. Although I keep going with one of them for simplicity reasons. Anyway, great explanation! Highly appreciated your contents. Keep goin and merry Xmas!
Thanks! Merry Christmas 🎄 Yep totally fine to use Riverpod, Provider, etc. 👍
Riverpod State Management Tutorial: th-cam.com/video/8H3bwxxla4Y/w-d-xo.html
Provider State Management Tutorial: th-cam.com/video/kN9Yfd4fu04/w-d-xo.html
@@HeyFlutter meanwhile I switched to bloc + get_it ;) just trying out different stuff
Thanks for the explaination !
I'll admit that you writing "stfu" to use autocompletion to write StatefulWidget made be chuckle xD
Thank you, @fgreau! 🙂
First of all thank you for this content bro here is question 06:30 when i add final String name; as varaiable on dependonMyinheritedWigetExactype() will i also change it to dependonMyinheritedWigetExactype().name ? 💁♀
Instead of putting a StatefulWidget on top of the InheritedWidget, couldn't you have just extracted the counter into a separate class with an increment method?
thx! great video!
You are welcome, Роман Сергеевич!
Absolutely brilliant keep going forward
Very well explained. Thanks! As a newcomer I have to say - clearly Flutter has big problem with state management. I know there are 3rd party packages, but c'mon.. there should be a better, clean way.
Right, @zledwon! 🙂
As far as I can tell, we are storing the state inside the InheritedWidget twice. Once from the Stateful widget, and one inside the InheritedWidget itself.
The only time we use the state inside the InheritedWidget, is when we check between current and previous state inside updateShouldNotify.
So what we do is keep two states in sync. When the stateful widget updates, it creates a new InheritedWidget which will trigger an updateshouldNotify, which will trigger a UI update.
Is that correct?
Thank You @KostasOreopoulos! Follow this link: semaphoreci.com/blog/state-management-flutter-inheritedwidget-provider-state-management#:~:text=InheritedWidget%20is%20a%20tool%20for,the%20use%20of%20the%20context.
I hope you will get your answer 🙂
for those who can't access the counter, add .counter after Updating.of(context) after this. ex: final counter = Updating.of(context).counter;
15 mins in ....I think i need to come back here later
Great, Thank you @shaderone07!
Dart seriously needs to DataClasses from python
Great explanation. In depth. Thanks.
good. bought ur sponsorship!
Best explanation about inherited widget🤘👌
Thank you✨️🙏
You are welcome, @hemantchauhan6437 😊
Most ppl nowadays are visual learners. So was wondering why they do not have the views and constrains tabs for Flutter development like in Java/Kotlin for Android Studio. They are very confusing building apps in the style of React when u have too many views.
you don't really need it as you can instantly see the changes reflect in the emulator or an actual device
thank Johannes
my concern is probably linked to an inheritedWidget.
the link to the source code does not work.
like having the new link?
Thanks, e.NONO! 🙂 This link should work for the source code: github.com/JohannesMilke/inherited_widget_example
Awesome vid..
oh my god you cant even imagine how much you helped me here....
Glad it was helpful, @moulikgupta6979 😀
Thank you for this, head and shoulders above other Inherited widget info.
You are welcome, AnchorRealtyNM!
Thank you for the good video.
As a note: so if I am correct, a drawback of InheritedWidget is, if your InheritedWidget is not above your MaterialApp and you push a page, then the children widgets will not be able to access the state variables of the InheritedWidget anymore. But if you put it above the MaterialApp then all ancestors and children will be able to access the state variables in the InheritedWidget. So how does one go about fixing the problem when a page is pushed and the InheritedWidget's state becomes inaccessible, because I am guessing this is due to the Navigator?
Thank You J Richards! Follow this link: medium.flutterdevs.com/inherited-widget-in-flutter-604b0f009297#:~:text=In%20flutter%2C%20the%20inherited%20widget,references%20when%20a%20change%20occurs.
I hope you will get your answer 🙂
@@HeyFlutter thank you Johannes!
Really well explained... But if I feel more comfortable just using provider than this... Will I be missing out on something??
@@HeyFlutter I actually agree with that logic. I too believe first learn to code those basics.. Then pick up on packages, lib.. Etc etc.. Hey by the way wrote you a email.. Hope you were able to read it.
Most state managements make use of the InheritedWidget, also the Provider. The Provider is only wrapping the InheritedWidget and has some more features for more comfortable usage.
Therefore it is always good to learn the basics of the InheritedWidget because it is used almost everywhere under the hood.
Thanks bro it's very helpful to understand inheritedWidet
Glad I could be of help, Thank you fethi sert! 😊
@@HeyFlutter I want to ask something what is deference between initilazing variable in InitState() and intiliazing normaly like under the Class
class Number extends StlsW{
int x = GetNumber()
}
//or
late int x;
initState(){
x = GetNumber();
}
@@HeyFlutter Yes you are very good but fast : )