Sync Notify Pattern for WPF Cross Thread View Model

WPF has a powerful data binding mechanism, by which it is easy to implement MVVM and MVC pattern for UI application.
But thing gets not so beautiful once you introduced multi-thread into the app. Somehow, it means you have to manually call dispatcher method to synchronize the thread context, or else INotifyPropertyChanged contract causes cross thread violation, which is likely to drive UI component throw exception. But tons of calls to Dispatcher.Invoke or Dispatcher.BeginInvoke make you code ugly and hard to maintain. And it is boring to call dispatcher everytime you try to write view model properties.

Is there any solution to this embarrassed situation?
The answer is Sync Notify pattern.

By analyzing the WPF data binding data flow, you can find the best point to behave the thread synchronization is at the boundary of your code and WPF implementation, which is the property changed  event raiser. To sync the thread context here makes your code clean and effective.

Typically, you might implement the INotifyPropertyChanged in following way:

        #region INotifyPropertyChanged Members         public event PropertyChangedEventHandler PropertyChanged;         protected void Notify(string propertyName)         {             if (PropertyChanged != null)                 PropertyChanged(this, new PropertyChangedEventArgs(propertyName));         }         #endregion

And you might implement the property of view model as following:

        #region Notify Property ViewModelProperty         private string viewModelPropertyBackField;         public string ViewModelProperty         {             get { return viewModelPropertyBackField; }             set             {                 if (viewModelPropertyBackField == value)                     return;                 viewModelPropertyBackField = value;                 Notify("ViewModelProperty");             }         }         #endregion

This implementation works perfect in single thread context , but fails in multi-thread context. So we introduce a new event raiser implementation, which synchronize the thread context before raising the event:

        #region Sync INotifyPropertyChanged Members         protected void SyncNotify(string propertyName, bool wait = false, Dispatcher dispatcher = null)         {             if (PropertyChanged == null)                 return;             dispatcher = dispatcher ?? System.Windows.Threading.Dispatcher.CurrentDispatcher;             if (dispatcher.Thread == Thread.CurrentThread)             {                 PropertyChanged(this, new PropertyChangedEventArgs(propertyName));             }             else             {                 if (wait)                 {                     dispatcher.Invoke(PropertyChanged, this, new PropertyChangedEventArgs(propertyName));                 }                 else                 {                     dispatcher.BeginInvoke(PropertyChanged, this, new PropertyChangedEventArgs(propertyName));                 }             }         }         

Posted via email from 米良的实验室

Self Registration Pattern for Singleton View Models in WPF

Where to store the Singleton View Model in WPF application, there are 2 common options:

1. Store in Resource Dictionary.

UI Designers prefers to store the WPF View Model into the Resource Dictionary because the objects in Resource Dictionary can be easily referenced in XAML. 

But Developers must hate that way very much! 

To fetch the object in Resource Dictionary from code behind must call the "FindResource" method of DependencyObject.  And codes with tons of calls to "FindResource" method are ugly and very low efficient. The situation is worse since the accessibility to object in resource dictionary  is also constrained by the Resource Scope, which means it is almost impossible to fetch the object from business logic. 

2. Store in the Static Class.

I preferred to store the View Model in static class which is available globally. Developer can fetch the object by calling the static method, and designer also can fetch the object by using {x:Static} psudo-tag.

But it is still inconvenient somehow for designer, and it is somehow hard to provide design-time mockup data in this way.

For the previous 2 solutions, the pros and cons are obvious. But is it possible to combine these 2 approaches together to gains all the advantages but all the disadvantages. 

The answer is Self-Registration Pattern.

The basic idea for Self-Registration Pattern is simple. It is obvious that we prefers to store the view models in Resource Dictionary, but we also want to access that object from Code Behind by calling static method.

So I designed the ViewModel class as following:

    public class ViewModel     {         #region Self Registration         public static ViewModel Default { get; private set; }         public ViewModel()         {             Default = this;         }         

Posted via email from 米良的实验室