There are is now an enum with four values: infrastructure along with several other fixes and improvements. After only 2 months and nearly 300 commits, this is one of the feature-richest releases we’ve ever done.This release, again, contains some breaking changes.The combo box is defined in XAML as follows: Here's what happens if we try to change selection from January to February under . The property changed notification on line 3 is no longer ignored, it is followed by the on lines 5 and 6.

wpf combobox binding selecteditem not updating-45wpf combobox binding selecteditem not updating-54

The property that sets the window brush for an inactive window. We’ve rewritten the has been completely rewritten, to fix a number of issues that have accumulated over time.

See PR #1320 The overlay behavior of the elements of the window titlebar can now be controlled individually. For a complete list of fixes, see PR #1156 Flyouts now have an option to be automatically closed when the user clicks outside of the flyout. Metro documentation site lives at instead of Apps. The old links should still work and redirect to the top level domain.

From the other hand, if we just let it change this will have a bad effect on the rest of the application.

The solution is to create a "double-buffer" property with two heads: the one facing the UI and the other facing the rest of the application.

Unfortunately, it turns out that if one uses MVVM and data binding, reverting user seletion in a combo box is difficult in . Unfortunately, the synchronization is broken in different ways in . Roughly, the combo box turns "deaf" to view model updates for the duration of "selection changed" windows message, probably to prevent infinite loops.

The combo box will report one thing to the application and show different thing to the user. Evidently, the combo box usually does listen to view model updates, even in .Better handling for dialogs settings also with the already available `Show Metro Dialog Async` method ```csharp // create and show custom dialog with default settings await this.Show Metro Dialog Async(new Custom Base Metro Dialog()); // create and show custom dialog with own settings await this.I used to it to research the issue and understand how the internals work.Download Combo Box Selection (30K) The applicaion uses MVVM approach (actually, it's just VVM, since the "model" class is not present).The most elaborated piece of code is the setter for to show view model selection state on screen. By having two properties instead of one we can distinguish property reads by the combo box, that go to .