Skip to main content

...

....

C# WPF Tutorial - Forcing a Binding Update [Beginner]


Here's a common scenario - you've got a WPF control bound to a property that doesn't update when the value of the property changes. If the object you have access to doesn't implement INotifyPropertyChanged or use Dependency Properties, this can be a very common problem.

Fortunately for us, there's a fairly simple work-around to this issue. WPF gives us the ability to force an update to any binding. Let's jump right in with an example class:
public class MyClass
{
  public string MyString { get; set; }
}
 
As you can see, this object has no way to notify bound controls when a property changes. Here's some XAML that binds to the property, MyString.
<StackPanel Orientation="Horizontal">
  <Label Content="Property Value: " />
  <Label Content="{Binding MyString}"
          x:Name="_lblValue" />
</StackPanel>
 
All right, now some code to change the value of the property:
_myClass.MyString = "Some new text.";
 
What you'll notice is that when the value changes, the Label bound to the property doesn't update - this is because WPF has no way to know when the property changes. What we have to do is get a reference to the binding and tell it to update manually.
BindingOperations.GetBindingExpressionBase(
  _lblValue, Label.ContentProperty).UpdateTarget();
 
GetBindingExpressionBase will return the base class for all binding expressions. This means that if you're binding is something complicated - like a MultiBinding, this will still work. We have to pass the function the target object and property where the binding is applied. We then simply call UpdateTarget, which forces the target to update with the source. Once this is called, our label will display the new value.

I hope this helps someone out there that has encountered this issue. 

Source Files:

Comments

Popular posts from this blog

C# Snippet - Shuffling a Dictionary [Beginner]

Randomizing something can be a daunting task, especially with all the algorithms out there. However, sometimes you just need to shuffle things up, in a simple, yet effective manner. Today we are going to take a quick look at an easy and simple way to randomize a dictionary, which is most likely something that you may be using in a complex application. The tricky thing about ordering dictionaries is that...well they are not ordered to begin with. Typically they are a chaotic collection of key/value pairs. There is no first element or last element, just elements. This is why it is a little tricky to randomize them. Before we get started, we need to build a quick dictionary. For this tutorial, we will be doing an extremely simple string/int dictionary, but rest assured the steps we take can be used for any kind of dictionary you can come up with, no matter what object types you use. Dictionary < String , int > origin = new Dictionary < string , int >();

C# WPF Printing Part 2 - Pagination [Intermediate]

About two weeks ago, we had a tutorial here at SOTC on the basics of printing in WPF . It covered the standard stuff, like popping the print dialog, and what you needed to do to print visuals (both created in XAML and on the fly). But really, that's barely scratching the surface - any decent printing system in pretty much any application needs to be able to do a lot more than that. So today, we are going to take one more baby step forward into the world of printing - we are going to take a look at pagination. The main class that we will need to do pagination is the DocumentPaginator . I mentioned this class very briefly in the previous tutorial, but only in the context of the printing methods on PrintDialog , PrintVisual (which we focused on last time) and PrintDocument (which we will be focusing on today). This PrintDocument function takes a DocumentPaginator to print - and this is why we need to create one. Unfortunately, making a DocumentPaginator is not as easy as

C# WPF Tutorial - Implementing IScrollInfo [Advanced]

The ScrollViewer in WPF is pretty handy (and quite flexible) - especially when compared to what you had to work with in WinForms ( ScrollableControl ). 98% of the time, I can make the ScrollViewer do what I need it to for the given situation. Those other 2 percent, though, can get kind of hairy. Fortunately, WPF provides the IScrollInfo interface - which is what we will be talking about today. So what is IScrollInfo ? Well, it is a way to take over the logic behind scrolling, while still maintaining the look and feel of the standard ScrollViewer . Now, first off, why in the world would we want to do that? To answer that question, I'm going to take a an example from a tutorial that is over a year old now - Creating a Custom Panel Control . In that tutorial, we created our own custom WPF panel (that animated!). One of the issues with that panel though (and the WPF WrapPanel in general) is that you have to disable the horizontal scrollbar if you put the panel in a ScrollV