So, it’s been another month since we released Catel 3.0. This means that soon, we will release a new version, and it will be 3.1. You can grab the latest version:
Below is a list of the most important changes.
OnDataContextChanged and OnPropertyChanged methods
Since lots of people need to write handlers (but forget to unsubscribe thus cause memory leaks), we made these available as default to all controls that Catel provides.
AsynchronousCommand
Asynchronous development becomes more and more important. In the latest version, we proudly introduce the AsynchronousCommand, which is a command that runs in the background and doesn’t block and UI. It is able to provide thread-safe callbacks to the UI as well.
You can read all about it in the official docs.
Memento pattern
The memento pattern is something hardly any custom made application implements due to its complexity. Catel now includes a memento service which allows to undo/redo changes on properties, collections and custom actions.
If you ever need to build in undo/redo support, this is what you are looking for! You can read all about it in the official docs.
Note that this feature is also available for non-xaml solutions
Improved handling of datacontext changes for nested user control scenarios
If you are using Catel, you are probably aware that you sometimes get false reports of binding errors. Catel now uses an improved way of determining the right datacontext in nested user control scenarios so these false errors no long appear in your output window.
What to expect next?
We are currently investigating what it takes to port Catel to WinRT. However, since reflection in WinRT is very basic (for example, we cannot get the name of a method), it is really hard to implement the WeakEventListener and MessageMediator in WinRT. However, we will keep trying…
You can also checkout the road map.
Subscribe