Wpf binding not updating source
However, if the object has changed such that representing it by a simple string is not descriptive enough, then there is a big problem.Let’s contrive a gnarly little sample class to serve as our data source that just holds a single property: property changes! Because it has no way of knowing; it fetches the property value just once as it initializes itself and renders itself on-screen. We can use Dependency Properties, but for now why don’t we just reach for the simplest way available.Change your source class to implement the interface.Take careful note of the change in your Now run your app and you should be seeing your GUI fields updating themselves to track the changes in your source class.
This is the simplest example of a one-way binding and handles probably the majority of cases of this nature. Please shoot back a note to me if you spot any mistakes, problems or additional insight.
This makes it send a notification to your XAML-defined Text Box of any important changes whenever you set a new value for that property.