I've incorporated this change into my project and now my List Views are behaving exactly how I want them to!In the previous article we saw how changes in a Text Box was not immediately sent back to the source.WPF suggested I could use an attached behavior to encapsulate what I'd done into something that would be even simpler to use from XAML and wouldn't require the developer's involvement at all (aside from referencing the code that implements the attached behavior, of course).Attached behaviors are a powerful technique that allow the introduction of changes to the functionality of a control simply by setting an attached property on it.The first one is set to Explicit, which basically means that the source won't be updated unless you manually do it.
The XAML looks like this: I'd arrived at the above solution and was going to consider the problem solved - and that's when Dr.
Instead, the source was updated only after focus was lost on the Text Box.
This behavior is controlled by a property on the binding called Update Source Trigger.
:) Okay, so if you're still reading, then your scenario is probably like mine: changes to the data source can occur without the application explicitly knowing about it.
That last bit may not make a lot of sense until you realize that it's possible to implement a great deal of an application's functionality entirely in XAML.