Mobile XAML - Revision history

CWI: /* Known issues */

2026-08-31T11:06:19Z

‎Known issues

CWI: /* DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} */

2026-08-26T12:56:33Z

‎DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}}

CWI: /* DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} */

2026-08-26T10:33:18Z

‎DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}}

CWI: /* DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} */

2026-08-26T10:19:15Z

‎DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}}

CWI: /* DataTrigger Issues */

2026-08-26T10:12:03Z

‎DataTrigger Issues

REP: /* Labels */

2026-08-06T13:57:14Z

‎Labels

CWI: /* Known issues */

2026-05-07T10:19:05Z

‎Known issues

CWI: /* Tooltips not supported on some iOS devices {{Version/MobileSince|5.0}} */

2026-05-07T08:49:55Z

‎Tooltips not supported on some iOS devices {{Version/MobileSince|5.0}}

CWI: /* Tooltips not supported on some iOS devices {{Version/MobileSince|5.0}} */

2026-05-06T13:38:41Z

‎Tooltips not supported on some iOS devices {{Version/MobileSince|5.0}}

CWI: /* Known issues */

2026-05-06T13:28:47Z

‎Known issues

@@ Line 598: / Line 598: @@
 ==== DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} ====
@@ Line 619: / Line 617: @@
 {{Hint|Use a DataChangedBehavior with SetPropertyAction instead of a DataTrigger if the property it sets should remain user-changeable afterwards. Keep DataTrigger/Style.Triggers only for properties that should stay continuously data-driven and don't conflict with user input.}}
-[[Category:Client|Xamarin XAML]]
-[[Category:Mobile|Mobile XAML]]
-[[Category:Pages with broken file links|Xamarin XAML]]
-[[Category:Styling|Xamarin XAML]]
-[[Category:XAML|Xamarin XAML]]
 === Incorrect glyphs may be shown on buttons ===

@@ Line 606: / Line 606: @@
 {{Hint|Maui ranks a value applied by an active DataTrigger's Setter higher than a manual property write (e.g. a user's tap). Every manual write attempt is silently discarded while the trigger's condition remains true.}}
-In the example below a DataTrigger is used to set the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab. Tapping another tab header highlights it, but the content never switches, and SelectedIndex silently reverts.
+One common use case that cannot be used directly in Maui is [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Pre-selecting_a_tab_based_on_a_metaclass_or_property|Pre-selecting a tab based on a metaclass or property]].
-As a workaround, do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead.
+As a workaround, do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead. For an example click [[HowTo:Convert_Xamarin_XAMLs_to_Maui#Pre-selecting_a_tab_based_on_a_metaclass_or_property|here]].
-−
-{| class="wikitable" style="width:100%; table-layout:fixed;"
-! style="width:50%;" | Xamarin
-! style="width:50%;" | MAUI
-|-
-−
-<syntaxhighlight lang="xml">
-<controls:UBIKTabView.Triggers>
-    <DataTrigger TargetType="controls:UBIKTabView"
-                 Binding="{Binding Content.MetaUID, Converter={StaticResource EqualityToBool}, ConverterParameter='b82accb3-7437-429d-aed9-08dfdd5a9e59'}"
-                 Value="True">
-        <Setter Property="SelectedIndex" Value="1" />
-    </DataTrigger>
-</controls:UBIKTabView.Triggers>
-</syntaxhighlight>
-||
-<syntaxhighlight lang="xml">
-xmlns:behaviors="clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI"
-...
-<controls:UBIKTabView.Behaviors>
-    <behaviors:DataChangedBehavior
-        Binding="{Binding Content.MetaUID, Converter={StaticResource EqualityToBool}, ConverterParameter='b82accb3-7437-429d-aed9-08dfdd5a9e59'}"
-        ComparisonCondition="Equal"
-        Value="True">
-        <behaviors:SetPropertyAction
-            PropertyName="SelectedIndex"
-            TargetObject="{Binding Source={x:Reference ContentTabs}}"
-            Value="1" />
-    </behaviors:DataChangedBehavior>
-</controls:UBIKTabView.Behaviors>
-</syntaxhighlight>
-|-
-|}
 {{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, for example:}}

@@ Line 600: / Line 600: @@
 {{UnderConstructionStart}}
-=== DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} ===
+==== DataTrigger permanently blocks manual changes {{Version/MobileSince|5.0.0}} ====
 A DataTrigger that sets a property the user can also change interactively will permanently block that manual change as long as the trigger's condition stays true. This did not happen in Xamarin - it is a Maui-specific behavior change.

@@ Line 608: / Line 608: @@
 In the example below a DataTrigger is used to set the selected tab based on the record's metaclass. The initial selection works correctly, but afterwards the user can never manually switch to a different tab. Tapping another tab header highlights it, but the content never switches, and SelectedIndex silently reverts.
-'''Workaround:''' Do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead.
+As a workaround, do not use DataTrigger for a property that should be data-driven once and then freely user-editable afterwards. Use the existing '''DataChangedBehavior''' and '''SetPropertyAction''' pattern instead.
 {| class="wikitable" style="width:100%; table-layout:fixed;"
@@ Line 643: / Line 643: @@
 |}
-{{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, e.g.:}}
+{{Attention|This is not limited to tab selection. The same problem can occur wherever a DataTrigger, Trigger, MultiTrigger sets a property that a user (or code-behind) is also meant to change afterwards, for example:}}
-* Selection controls: Picker.SelectedIndex/SelectedItem, CollectionView/ListView.SelectedItem, RadioButton.IsChecked, Shell.CurrentItem
+* Selection controls: Picker.SelectedIndex/SelectedItem, ListView.SelectedItem, RadioButton.IsChecked
 * Toggle/input controls: Switch.IsToggled, CheckBox.IsChecked, Entry/Editor.Text
 * Expand/collapse state on any control the user can also expand/collapse manually
@@ Line 650: / Line 650: @@
 * Code-behind writes executed after the trigger has already applied a value (not just touch input)
-{{Hint|When converting a Xamarin DataTrigger, if the property it sets should remain user-changeable afterwards, convert it into a DataChangedBehavior with SetPropertyAction. Keep DataTrigger/Style.Triggers only for properties that should stay continuously data-driven and don't conflict with user input.}}
+{{Hint|Use a DataChangedBehavior with SetPropertyAction instead of a DataTrigger if the property it sets should remain user-changeable afterwards. Keep DataTrigger/Style.Triggers only for properties that should stay continuously data-driven and don't conflict with user input.}}
 {{UnderConstructionEnd}}

@@ Line 596: / Line 596: @@
 <br>
 <br>
 === Incorrect glyphs may be shown on buttons ===

@@ Line 275: / Line 275: @@
 === Labels ===
-* Use [https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/text/label#formatted-text FormattedText] instead of multiple labels.
+* Use [https://learn.microsoft.com/en-us/dotnet/maui/fundamentals/data-binding/multibinding?view=net-maui-10.0 MultiBinding] instead of multiple labels.
 * Use [https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.linebreakmode?view=xamarin-forms Linebreakmode] NoWrap (which is already the default).
 * Avoid [https://docs.microsoft.com/en-us/dotnet/api/Xamarin.Forms.Label.VerticalTextAlignment?view=xamarin-forms VerticalTextAlignment]. Anyway, if needed, use VerticalTextAligment instead of
@@ Line 286: / Line 287: @@
 </syntaxhighlight >
+[[Category:Client|Xamarin XAML]]
+[[Category:Mobile|Mobile XAML]]
+[[Category:Pages with broken file links|Xamarin XAML]]
+[[Category:Styling|Xamarin XAML]]
+[[Category:XAML|Xamarin XAML]]
 === Images ===

@@ Line 695: / Line 695: @@
 === Tooltips not supported on mobile iOS devices {{Version/MobileSince|5.0}} ===
 On iOS, native tooltips are only supported under very specific conditions. According to the official [https://learn.microsoft.com/en-us/dotnet/maui/user-interface/tooltips?view=net-maui-10.0| Microsoft documentation], tooltips are only shown when running the app on macOS with a pointer device. On physical iPhones and iPads, tooltips are generally not displayed. This means that using ToolTipProperties in XAML will not work reliably on iOS mobile devices.
@@ Line 737: / Line 736: @@
 </Border>
 </syntaxhighlight>
 [[Category:Client|Xamarin XAML]]

← Older revision		Revision as of 13:28, 6 May 2026
Line 695:		Line 695:


		+	{{UnderConstructionStart}}
		+	=== Tooltips not supported on some iOS devices {{Version/MobileSince\|5.0}} ===
		+	On iOS, native tooltips are only supported under very specific conditions. According to the official [https://learn.microsoft.com/en-us/dotnet/maui/user-interface/tooltips?view=net-maui-10.0\| Microsoft documentation], tooltips are only shown when running the app on macOS with a pointer device. On physical iPhones and iPads, tooltips are generally not displayed. This means that using ToolTipProperties in XAML will not work reliably on iOS mobile devices.
		+
		+	A possible workaround is to simulate tooltip behavior using a [https://help.syncfusion.com/maui/popup/overview\| SfPopup control]. The idea is to use a tap interaction on the UI element (e.g., via a ''TappedBehavior'' with a ''SetPropertyAction'') that opens a Popup positioned relative to that element, and to automatically close the Popup after a short duration.
		+
		+	<syntaxhighlight lang="xml">
		+	<!-- AFTER WORKAROUND -->
		+	xmlns:sfPopup="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup"
		+	xmlns:behaviors="clr-namespace:UBIK.MAUI.Behaviors;assembly=UBIK.MAUI"
		+
		+	<sfPopup:SfPopup
		+	x:Name="TooltipTextPopup"
		+	AutoCloseDuration="3000"
		+	RelativePosition="AlignTop"
		+	RelativeView="{x:Reference YourUIElement}"
		+	ShowHeader="False">
		+	<sfPopup:SfPopup.ContentTemplate>
		+	<DataTemplate>
		+	<Label Text="This will be displayed as Tooltip text" />
		+	</DataTemplate>
		+	</sfPopup:SfPopup.ContentTemplate>
		+	</sfPopup:SfPopup>
		+
		+	<Border x:Name="YourUIElement">
		+	<Border.Behaviors>
		+	<behaviors:TappedBehavior>
		+	<behaviors:SetPropertyAction
		+	PropertyName="IsOpen"
		+	TargetObject="{Binding Source={x:Reference TooltipTextPopup}}"
		+	Value="True" />
		+	</behaviors:TappedBehavior>
		+	</Border.Behaviors>
		+	</Border>
		+
		+	<!-- BEFORE WORKAROUND -->
		+	<Border x:Name="YourUIElement">
		+	<ToolTipProperties.Text>
		+	This will NOT be shown on iOS
		+	</ToolTipProperties.Text>
		+	</Border>
		+	</syntaxhighlight>
		+
		+	{{Attention\|The ''IsOpen'' property on the SfPopup only indicates whether the Popup is open or closed, but it does not replace ''IsVisible''. If there is any Visibility dependency related to other controls, make sure to also set the ''IsVisible'' property on the SfPopup accordingly to prevent possible issues.}}
		+
		+	{{UnderConstructionEnd}}
		+
		+	[[Category:Client\|Xamarin XAML]]
		+	[[Category:Mobile\|Mobile XAML]]
		+	[[Category:Pages with broken file links\|Xamarin XAML]]
		+	[[Category:Styling\|Xamarin XAML]]
		+	[[Category:XAML\|Xamarin XAML]]

	= UBIK Go (Maui) Customizing Guide {{Version/MobileSince\|5.1}} =		= UBIK Go (Maui) Customizing Guide {{Version/MobileSince\|5.1}} =