Wpf command canexecute not updating
Show Metro Dialog Async(new Custom Base Metro Dialog(this.metro Dialog Settings)); // or await this.Show Metro Dialog Async(new Custom Base Metro Dialog(this, this.metro Dialog Settings)); This is the first stable release of Mah Apps. We removed everything marked as obsolete and made some API changes, but from now on Mah Apps.Strictly speaking it's actually the way you use it that causes the leak.If you have a child object that data binds to a property of its parent, a memory leak can occur. The condition will only occur if the bound property is a Property Descriptor property, as Children. This is because, in order to detect when a Property Descriptor property changes, the framework has to subscribe to the Value Changed event, which in turn sets up a strong reference chain.Everything would still work, and your code will not be broken, but you would not have that nice reassurance of having a strongly typed parameter in the Delegate Command. Once again, this only impacts you if you are calling Execute manually in code. I don’t think this is a big deal, but I would love to know what you think.This change impacts every single Prism application out there, so it important that you let your voice be heard. I don’t like to make breaking changes, but sometime in order to move a framework forward, to fix an major issue, or to improve its value, it is necessary.Metro follows Semantic Versioning, at least API wise.Please note that minor visual changes can still occur if there’s a need for them.
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.Subscribing to an event on a static object will set up a strong reference to any objects handling that event.Statics, one referenced, remain for the duration of the app domain execution, and therefore so do all their references. So it really provides absolutely no benefit to you. Not to mention the fact that the ICommand is not executed by any XAML framework in an async manner.