Changes
Restructured wiki from most to least important, added SfTabView and PTR under Mandatory
=== SfTabView ===
==== Namespace Update ====
'''Update Syncfusion TabView namespace.'''
Replace the Xamarin namespace with the MAUI equivalent.
|}
==== Remove Obsolete Converters ====
'''Remove ItemCountToBoolConverter from Resources.'''
This converter is no longer usable in TabView headers.
|}
==== Add StringFormatConverter ====
'''Use StringFormatConverter for combined header strings.'''
Syncfusion MAUI TabView uses a single `Header` property instead of templates.
⚠️ Avoid using bindings in `Parameter1` and `Parameter2` — use static strings only. For complex cases, use `EvalExpression`.
==== FontImageSource Styling ====
'''Add local style for FontImageSource.'''
Global styles are not supported.
|}
==== TabView Structure ====
'''Use Grid to wrap TabView.'''
MAUI TabView requires a different structure and property set.
|}
==== Property Changes ====
'''Update renamed or removed properties.'''
=== SfPullToRefresh ===
'''It is recommended to get rid of all SfPullToRefresh controls due to some issues that might occur.''' For more information refer to [[Mobile_XAML#Issues_with_SfPullToRefresh_in_MAUI|this article]]. In our Maui standard client, the PullToRefresh control has already been replaced by a Refresh button in the Context Menu, so there's no need for a custom Refresh button.
⚠️ '''If SfPullToRefresh is still required, the following points should be considered.'''
==== Namespace Update ====
'''Update Syncfusion TabView namespace.'''
Replace the Xamarin namespace with the MAUI equivalent.
|}
==== Rename SfPullToRefresh properties ====
'''Renamed in Maui, however, currently these properties cause an issue and should not be included in customizings.'''
SfPullToRefresh:
|}
==== Avoid multiple SfPullToRefresh controls ====
'''To prevent an issue that causes the app to freeze, avoid placing more than one SfPullToRefresh controls as siblings in a xaml hierarchy'''. If switching between contents in a SfPullToRefresh control is necessary use separate DataTemplates for the contents and use e.g. a DataTrigger to set one of them as the ControlTemplate of a ContentControl inside the SfPullToRefresh control.
|}
==== Avoid using SyncFusion ListViews directly in SfPullToRefresh controls ====
'''To prevent an issue on some Android devices that can cause some items in a SfListViewExt to be rendered incorrectly or not at all after triggering a PullToRefresh, avoid placing a SfListViewExt directly in a SfPullToRefresh control'''.
Instead, wrap the ListView in a DataTemplate and use it in a ContentControl as a child of the SfPullToRefresh control, as shown in the Xaml example below.
