I have a WPF view with a TextBox, binding the Text field to a ViewModel with UpdateSourceTrigger set to PropertyChanged. In the property setter in the ViewModel, I have a simple check to prevent the text from exceeding 10 characters:
<TextBox Text="{Binding Name, UpdateSourceTrigger=PropertyChanged, Mode=TwoWay}" />
public partial class MainWindow : Window
{
public MainWindow()
{
InitializeComponent();
this.DataContext = new MainViewModel();
}
}
public string Name
{
get { return _Name; }
set
{
if (_Name != value)
{
if (value.Length <= 10)
{
_Name = value;
}
RaisePropertyChanged("Name");
}
}
}
If the value isn’t set, I still RaisePropertyChanged (which simply fires PropertyChanged).
The problem is that when I type in the 11th character in the UI, I don’t update _Name. I fire PropertyChanged, and I can see the get accessor get called and it returns the string with only 10 characters. However, my TextBox doesn’t reflect this; it still shows the string with 11 characters.
On top of that, is that if on the 11th character I change the text in the setter to “ERROR”, and fire property changed, the TextBox DOES update to show the altered text.
So why is it that if I alter the text in the setter back to the previous value, the UI doesn’t reflect this?
I know there are alternative ways of handling max characters, but why won’t this work?
This is nothing but a bug in the framework. The
Textproperty in theTextBoxdoes get your new value but the GUI is now out of sync with its ownTextProperty. This also happends for anyItemsControlwhen you want to cancel a change ofSelectedItemfrom the ViewModel and it’s really annoying.This bug doesn’t happend when you use explicit
Bindingthough so this can be used as a workaround.Xaml
Code behind
To verify that the TextBox GUI indeed is out of sync, just observe the value of
TextBox.Text. TheTextBoxwill say “123456789___0” for example whileTextBlocksays “123456789”.