This is a really simple question, but I was wondering if someone could explain what the 4th line is actually doing? so the first line gives an event to the handler. I don't really know in what circumstances handler will return null or what the last line does.
When you pass the handler your object and which property changed, what does it do with them?
PropertyChangedEventHandler handler = PropertyChanged; //property changed is the event
if (handler != null)
{
handler(this, new PropertyChangedEventArgs(name));
}
I assume I used this to get this code but I would like to understand what it is doing fully.
PropertyChanged
is the event that was declared like this, according to its definition in the interface:Events that are defined like that are actually a syntactic sugar for a list of event handlers you can add a delegate (that is a reference to a function) to by subscribing, or remove a delegate by unsubscribing.
Now, when you call an event, i.e.
PropertyChanged(...)
, then what happens internally is that every delegate in that internal list is called separately with the parameters. This will tell all the subscribers of your event that the event happened.Now, the reason for the whole thing with the
handler
variable is, thatPropertyChanged
can be null. If nothing subscribed to it, then calling the event (or rather the event handler list) would not work, so this is just a way to ensure that you can actually execute the handler.If you just did:
you would get a
NullReferenceException
if no one was subscribed to the eventPropertyChanged
. To counteract this you add a null check:Now, if you are using multi-threading someone could unsubscribe between the null check and the calling of the event, so you could still get a
NullReferenceException
. To handle that we copy the event handler to a temporary variableNow if someone unsubscribes from the event our temporary variable
handler
will still point to the old function and this code now has no way of throwing aNullReferenceException
.Most often you will see people use the keyword
var
instead, this makes it so you don't need to type in the full type of the temporary variable, this is the form you will see most often in code.handler
can be null if no handlers are subscribed to the event, the fourth line raises the event for the property name given (which executes all subscribed handlers).Usually the WPF framework will subscribe to
PropertyChanged
when you use bindings, so it can update the binding once the bound property changes.