Hi. Your example works, but I don't understand why. Where some method suscribes to the event PropertyChanged? Where this assignation happens: PropertyChanged+= SomeMethod; ? Thanks
I am tired today and for some reason I thought the video title said, what is the issue of INotifyPropertyChanged. So I am watching it but there is no issue HAHA.
Lots of these youtube tutorials on INotifyPropertyChanged have people asking the same question - where is PropertyChanged event implemented so that it isn't null. I suspect that the framework has implemented the event for each item that is bound to that other property. You don't see it here. You are firing an event into the binding structures at runtime. Probably the best question to ask is - what other properties do I want to update as a consequence of this property being set. If binding has been set on that property, there will be an event handler behind the smoke and mirrors.
Hi. Your example works, but I don't understand why. Why PropertyChanged is not null? Who setted it? Where some method suscribes to it? Where this assignation happens: PropertyChanged+= SomeMethod; ? Thanks
This explains clearly the INotifyPropChanged , Thanks for your contribution , Please keep posting such videos
Most Underrated Video. Perfect Explanation Straight to the Point. Awesome. It's time for me to subscribe to your channel.
thanks Sir, you saved my life
Thanks for the concise explanation.
Hi. Your example works, but I don't understand why. Where some method suscribes to the event PropertyChanged? Where this assignation happens: PropertyChanged+= SomeMethod; ? Thanks
works just in wpf or i can implement them into winforms too ?
I am tired today and for some reason I thought the video title said, what is the issue of INotifyPropertyChanged. So I am watching it but there is no issue HAHA.
Lots of these youtube tutorials on INotifyPropertyChanged have people asking the same question - where is PropertyChanged event implemented so that it isn't null. I suspect that the framework has implemented the event for each item that is bound to that other property. You don't see it here. You are firing an event into the binding structures at runtime. Probably the best question to ask is - what other properties do I want to update as a consequence of this property being set. If binding has been set on that property, there will be an event handler behind the smoke and mirrors.
Very fantastic explanation mate, keep it up!
Hi. Your example works, but I don't understand why. Why PropertyChanged is not null? Who setted it? Where some method suscribes to it? Where this assignation happens: PropertyChanged+= SomeMethod; ? Thanks
Very well explained man, thank you!
Thankyou sir 👏🏻😊
Great!!!
Excellent video, thanks!
I like Modi much better than Trump
haha
Please keep safe
You lost me at Trump.