Your before and after implementation of the ValueListenableBuilder + ValueNotifier makes it easy to understand the concept. How I wish every content creator does this pattern of teaching. Thanks for sharing!
This is really a well explained video. Could you explain ValueNotifier by passing an object of class which contain a int value instead of passing directly a int . I am bit confused with Passing my whole object value with ValueNotifier.
I'm implementing something similar for my flutter app development series. That video will be available on coming Wednesday. So hopefully that will help you.
I've published a package for doing exactly this, called MultiValueListenableBuilder. Unfortunately I haven't made a video on that package yet. But from the example, it should be easy to understand how to use it. Here is the link: pub.dev/packages/multi_value_listenable_builder
@@DevKage Yes. I looked at your package. It's great. You are amazing! 🙏 Wanted to understand one thing, I have used nested ValueListenableBuilder i.e., next ValueListenableBuilder inside builder of first ValueListenableBuilder. Like this total I have used total 3 nested ValueListenableBuilder. It's working. Could you please tell me, which one is better w.r.t. performance. Is your package better or nested ValueListenableBuilder.? Why am I asking is, nested ValueListenableBuilder took me 10 lines of code. Is it better to add package or these 10 lines of nested code.?
If you compare performance of my package and your nested code, most probably you'll not see any performance difference. This is because internally my package also uses nested ValueListenableBuilder widgets. 😅 Ignoring the fact that this package is written by me, I'll personally prefer writing my own code instead of using a package for simple cases. Having less dependencies is always better. 🤘🏻
It does not matter if ValueNotifier is defined on same page or on a page way before its use. As long as you make sure that the ValueNotifier object is fully initialized and non-null before using it as a 'listenable' in a ValueListenableBuilder() widget, everything should work just fine. If you want an example you can take a look at this video where I have defined 2 ValueNotifiers a members of a class and have used them on a totally different place. ua-cam.com/video/tZTaDc9QRm8/v-deo.html
Your before and after implementation of the ValueListenableBuilder + ValueNotifier makes it easy to understand the concept. How I wish every content creator does this pattern of teaching. Thanks for sharing!
Thanks man!🤘🏼
Excellent. Succinct and right to the point. You are a Flutter Rockstar! Keep going.
Thanks for those kind words!
Very good explanation
Thanks 🤘🏼
Great way of explanation👏👏
Glad to know that you liked it! Thanks for watching 🙂
Nice presentation!
Thanks!
Great, thank you
Thanks for watching!🤘🏼
That is great explanation. Thanks
Thanks!
Good content. I got what I was looking for. It was a bit over complicated on StackOverflow. Your version is easy. Keep it up!
Thanks for watching! Glad to know that it was helpful for you. 🙂
exceptional explaination.
Thanks☺️
Great 🔥
This is really a well explained video. Could you explain ValueNotifier by passing an object of class which contain a int value instead of passing directly a int . I am bit confused with Passing my whole object value with ValueNotifier.
I'm implementing something similar for my flutter app development series. That video will be available on coming Wednesday. So hopefully that will help you.
My target widget is dependent on 3 value notifiers. In that case how to use this ValueListenableBuilder.??
I've published a package for doing exactly this, called MultiValueListenableBuilder. Unfortunately I haven't made a video on that package yet. But from the example, it should be easy to understand how to use it. Here is the link: pub.dev/packages/multi_value_listenable_builder
@@DevKage Yes. I looked at your package. It's great. You are amazing! 🙏
Wanted to understand one thing, I have used nested ValueListenableBuilder i.e., next ValueListenableBuilder inside builder of first ValueListenableBuilder. Like this total I have used total 3 nested ValueListenableBuilder. It's working.
Could you please tell me, which one is better w.r.t. performance. Is your package better or nested ValueListenableBuilder.?
Why am I asking is, nested ValueListenableBuilder took me 10 lines of code. Is it better to add package or these 10 lines of nested code.?
If you compare performance of my package and your nested code, most probably you'll not see any performance difference. This is because internally my package also uses nested ValueListenableBuilder widgets. 😅
Ignoring the fact that this package is written by me, I'll personally prefer writing my own code instead of using a package for simple cases. Having less dependencies is always better. 🤘🏻
@@DevKage Thank you.🙏 ಡೆವ್ ಕಾಗೆ ಅವರು ಕನ್ನಡದವರಾ.?😀
I didn't get this completely, but no, it is not related to that. It is more like "Hokage" from the anime Naruto. 😅
how about using ValueNotifier on different page?
It does not matter if ValueNotifier is defined on same page or on a page way before its use. As long as you make sure that the ValueNotifier object is fully initialized and non-null before using it as a 'listenable' in a ValueListenableBuilder() widget, everything should work just fine. If you want an example you can take a look at this video where I have defined 2 ValueNotifiers a members of a class and have used them on a totally different place. ua-cam.com/video/tZTaDc9QRm8/v-deo.html
How to change the color
Which color?
Ohh, Look nice, but I didnt understant very well for putting on my own code, could you help me please? Can you tell me your email?
Sure why not. It's hellodevkage@gmail.com. You can also join this telegram group t.me/joinchat/OaRTa0zXZaJyjWOlUa2Wtw
@@DevKage okay, I will sent you a messege today :)