On my earlier post I wrote about “Building a dispatcher agnostic view-model”; that was just laying the ground for this follow up post, where I am going to show how we can extend that knowledge to use view-models shared between separate windows on different UI threads!
In truth, I started thinking in writing this after seeing my fellow MVP Rudy Huyn CrossUIBinding library.
Nice, but wouldn't it be easier just to override the add & remove of the PropertyChanged event and capture the Dispatcher there? That way all you need is a base viewmodel, no other changes on the view or properties of the viewmodel!
— Pedro Lamas (@pedrolamas) March 16, 2018
Rudy’s solution to this problem requires a wrapper around the properties of the view-models, where as I intend to fix the way view-models notify their event handlers.
But why do I need this?
Well, you will only need this if your application uses multiple windows and you want to share the same view-model instance between them!
if that is the case, then you must ensure you raise the INotifyPropertyChanged.PropertyChanged event on the correct thread as each window as its own separate UI thread!
I strongly recommend a look at the great document that Rudy has written around the CrossUIBinding as it has a lot of valuable information with some great visualizations!
So how do we solve this?
We can ensure we raise the PropertyChanged event in the correct UI thread by capturing the dispatcher instance when an event handler is added!
That can easily be achieved by defining custom add and remove event accessors that will get invoked when client code subscribes and unsubscribes respectively to the event:
public abstract class MultiWindowBaseViewModel : INotifyPropertyChanged
{
public event PropertyChangedEventHandler PropertyChanged;
{
add
{
// add code goes here
}
remove
{
// remove code goes here
}
}
}
All we now need is to ensure we capture the CoreDispatcher when the add method runs, and store that with the handler reference.
After my first post, Daniel Vistisen correctly pointed out that we can use SynchronizationContext instead of CoreDispatcher thus making the whole thing .NET Standard compliant:
Why not just use SynchronizationContext? Works with .netstandard
— Daniel Vistisen (@DanielVistisen) March 28, 2018
He is absolutely right, so that is what we will now do!
We will use a Dictionary<SynchronizationContext, PropertyChangedEventHandler> to keep a collection of event handlers for each SynchronizationContext.
In the end, this is what I got to:
public class MultiWindowViewModelBase : INotifyPropertyChanged
{
private readonly object _lock = new object();
private readonly Dictionary<SynchronizationContext, PropertyChangedEventHandler> _handlersWithContext = new Dictionary<SynchronizationContext, PropertyChangedEventHandler>();
public event PropertyChangedEventHandler PropertyChanged
{
add
{
if (value == null)
{
return;
}
var synchronizationContext = SynchronizationContext.Current;
lock (_lock)
{
if (_handlersWithContext.TryGetValue(synchronizationContext, out PropertyChangedEventHandler eventHandler))
{
eventHandler += value;
_handlersWithContext[synchronizationContext] = eventHandler;
}
else
{
_handlersWithContext.Add(synchronizationContext, value);
}
}
}
remove
{
if (value == null)
{
return;
}
var synchronizationContext = SynchronizationContext.Current;
lock (_lock)
{
if (_handlersWithContext.TryGetValue(synchronizationContext, out PropertyChangedEventHandler eventHandler))
{
eventHandler -= value;
if (eventHandler != null)
{
_handlersWithContext[synchronizationContext] = eventHandler;
}
else
{
_handlersWithContext.Remove(synchronizationContext);
}
}
}
}
}
protected void OnPropertyChanged([CallerMemberName] string propertyName = null)
{
KeyValuePair<SynchronizationContext, PropertyChangedEventHandler>[] handlersWithContext;
lock (_lock)
{
handlersWithContext = _handlersWithContext.ToArray();
}
var eventArgs = new PropertyChangedEventArgs(propertyName);
foreach (var handlerWithContext in handlersWithContext)
{
var synchronizationContext = handlerWithContext.Key;
var eventHandler = handlerWithContext.Value;
synchronizationContext.Post(o => eventHandler(this, eventArgs), null);
}
}
}
Now all we need is to ensure that any view-model used on multiple windows, inherits from this base class.
Here’s a really simple example:
public class MainViewModel : MultiWindowViewModelBase
{
private string _text;
public string Text
{
get { return _text; }
set
{
if (_text == value) return;
_text = value;
OnPropertyChanged();
}
}
}
Final thoughts
The ApplicationView.Consolidated event should be monitored to allow for proper cleaning, so that no memory leaks occur.
Here’s an example of how this can be achieved:
public sealed partial class MainPage : Page
{
public MainViewModel ViewModel => App.MainViewModel;
public MainPage()
{
DataContext = ViewModel;
this.InitializeComponent();
ApplicationView.GetForCurrentView().Consolidated += ApplicationView_OnConsolidated;
}
private void ApplicationView_OnConsolidated(ApplicationView s, ApplicationViewConsolidatedEventArgs e)
{
if (e.IsAppInitiated || e.IsUserInitiated)
{
s.Consolidated -= ApplicationView_OnConsolidated;
DataContext = null;
// this is only required if you are using compiled bindings (x:Bind)
Bindings.StopTracking();
}
}
}
I’ve also made available a full sample on GitHub so you can see and test the whole solution! :)
