Difference between revisions of "Version 3.6 (WinX)"

We have made some improvements to make some bindings in Xaml code easier and more efficient. Some changes to your existing Xaml customizings might be necessary. Please refer to each section to see if the change is mandatory or not.

Binding to TemplateService and the templates

This change is not mandatory and your existing Xamls will still work. We do recommend updating them, though.

Previously the TemplateService (the one providing access to all customizable templates) was only available on certain views (e.g. pages, dialogs, etc.). And the binding to it could only be done using named element like

<ContentControl ContentTemplate="{Binding ElementName=contentPage, Path=TemplateService.UBIKChildPageActionTemplate}" />

It is now made accessible from all view models (you can use the developer mode to check its availability). Also, you can now use the exact names of the template files as indexers for binding to those templates. Therefore, the binding can be changed to something like

<ContentControl ContentTemplate="{Binding TemplateService[UBIKChildPageAction]}" />

Use SelectionBoundListView instead of ListView

A SelectionBoundListView was already available in earlier versions but not mandatory. For performance improvements, it is now mandatory wherever you display UBIK^® content (objects, properties, etc.). You need to add a namespace like xmlns:uc="using:UBIK.WinX.Controls" to your Xaml file and use it like <uc:SelectionBoundListView ... />.

Technically speaking, SelectionBoundListView informs item view models when their corresponding items are visualized. This way, view models can skip a lot of unnecessary work (on the UI) when their views are not visible. If the regular ListView is used instead, the item views will not reflect content changes until the page is reloaded/refreshed.