XAML - Revision history

CWI: /* Custom VisualState Trigger {{Version/WinXSince|5.1.1}} */

2026-03-02T10:24:50Z

‎Custom VisualState Trigger {{Version/WinXSince|5.1.1}}

CWI: /* Custom VisualState Trigger {{Version/WinXSince|5.1.1}} */

2026-03-02T08:58:11Z

‎Custom VisualState Trigger {{Version/WinXSince|5.1.1}}

CWI: /* Custom VisualState Trigger {{Version/WinXSince|5.1.1}} */

2026-02-26T14:18:04Z

‎Custom VisualState Trigger {{Version/WinXSince|5.1.1}}

CWI: /* Custom VisualState Trigger {{Version/WinXSince|5.1.1}} */

2026-02-26T14:05:35Z

‎Custom VisualState Trigger {{Version/WinXSince|5.1.1}}

CWI: /* Miscellaneous */

2026-02-26T14:04:32Z

‎Miscellaneous

CWI: /* Specific {{UBIK}} Controls */

2025-11-27T10:35:34Z

‎Specific {{UBIK}} Controls

CWI: /* UBIKWebView {{Version/WinXSince|5.1}} */

2025-11-24T09:44:37Z

‎UBIKWebView {{Version/WinXSince|5.1}}

CWI: /* Basic */

2025-11-24T09:38:18Z

‎Basic

CWI: /* Differences between Mobile and UWP */

2025-09-23T07:41:33Z

‎Differences between Mobile and UWP

CWI: /* Differences between Mobile and UWP */

2025-09-23T07:38:40Z

‎Differences between Mobile and UWP

@@ Line 481: / Line 481: @@
 <br>
-=== Custom VisualState Trigger  {{Version/WinXSince|5.1.1}} ===
+=== Custom VisualState Trigger  {{Version/WinXSince|5.1}} ===
-{{UnderConstructionStart}}
-−
 The '''UBIKStateObserverTrigger''' (UWP only) is a custom State trigger that allows activating a Visual State based on a value. The trigger compares the '''StateObserver''' value with the specified '''ExpectedValue'''. If both values are equal, the corresponding VisualState becomes active. This enables clean, template-based UI state changes without attaching behaviors directly to controls. It is especially useful in scenarios where behaviors cannot be reused in styles due to framework limitations.
@@ Line 513: / Line 511: @@
 </Style>
 </source>
 [[Category:Mobile|XAML]]

@@ Line 484: / Line 484: @@
 {{UnderConstructionStart}}
-The '''UBIKStateObserver''' (UWP only) is a custom State trigger that allows activating a Visual State based on a value. The trigger compares the '''StateObserver''' value with the specified '''ExpectedValue'''. If both values are equal, the corresponding VisualState becomes active. This enables clean, template-based UI state changes without attaching behaviors directly to controls. It is especially useful in scenarios where behaviors cannot be reused in styles due to framework limitations.
+The '''UBIKStateObserverTrigger''' (UWP only) is a custom State trigger that allows activating a Visual State based on a value. The trigger compares the '''StateObserver''' value with the specified '''ExpectedValue'''. If both values are equal, the corresponding VisualState becomes active. This enables clean, template-based UI state changes without attaching behaviors directly to controls. It is especially useful in scenarios where behaviors cannot be reused in styles due to framework limitations.
 Custom states should be placed in a separate VisualStateGroup. States within the same group are mutually exclusive. If combined with standard groups such as CommonStates (Normal, Focused, PointerOver, etc.), the custom state may be overridden.
@@ Line 500: / Line 500: @@
                                <VisualState x:Name="CustomState">
                                     <VisualState.StateTriggers>
-                                          <trigger:UBIKStateObserver StateObserver="{Binding ValueItem.PropertyValue.IsSuggestedValue}" ExpectedValue="True" />
+                                          <trigger:UBIKStateObserverTrigger StateObserver="{Binding ValueItem.PropertyValue.IsSuggestedValue}" ExpectedValue="True" />
                                     </VisualState.StateTriggers>
                                     <VisualState.Setters>

@@ Line 503: / Line 503: @@
                                     </VisualState.StateTriggers>
                                     <VisualState.Setters>
-                                          <Setter Target="ExampleGrid.Foreground" Value="Red" />
+                                          <Setter Target="ExampleGrid.Background" Value="Red" />
                                     </VisualState.Setters>
                                </VisualState>

@@ Line 483: / Line 483: @@
 === Custom VisualState Trigger  {{Version/WinXSince|5.1.1}} ===
 {{UnderConstructionStart}}
 The UBIKStateObserver (UWP only) is a custom State trigger that allows activating a Visual State based on a value. The trigger compares the '''StateObserver''' value with the specified '''ExpectedValue'''. If both values are equal, the corresponding VisualState becomes active. This enables clean, template-based UI state changes without attaching behaviors directly to controls. It is especially useful in scenarios where behaviors cannot be reused in styles due to framework limitations.
 Custom states should be placed in a separate VisualStateGroup. States within the same group are mutually exclusive. If combined with standard groups such as CommonStates (Normal, Focused, PointerOver, etc.), the custom state may be overridden.
@@ Line 514: / Line 515: @@
 {{UnderConstructionEnd}}
 === UBIKContentControl ===

@@ Line 480: / Line 480: @@
 </tabs>
 <br>
 === UBIKContentControl ===
@@ Line 498: / Line 532: @@
 </tabs>
 <br>
 == Custom Icons ==

@@ Line 136: / Line 136: @@
 </tabs>
 ==== UBIKWebView {{Version/WinXSince|5.1}} ====
-As there is a bug in the WebView2 where specific links cannot be opened, we introduced the UBIKWebView, which contains a workaround for this issue.
+As there is a bug in the WebView2 (only in WinX/UWP) where specific links cannot be opened, we introduced the UBIKWebView, which contains a workaround for this issue.
 <br>
 Example:
@@ Line 145: / Line 144: @@
 <ctrls:UBIKWebView x:Name="WebContent" Source="{Binding DocumentViewModel.OnlineURI}" />
 </source>
-[[Category:Mobile|XAML]]
-[[Category:WinX|XAML]]
-[[Category:XAML|XAML]]
 === Advanced ===
@@ Line 155: / Line 153: @@
 Allows to evaluate a C# expression in XAML, using any amount of [[EvalExpression#Parameters|EvalExpressionParameters]]
+[[Category:Mobile|XAML]]
+[[Category:WinX|XAML]]
 == Converters ==

@@ Line 497: / Line 497: @@
 == Differences between Mobile and UWP ==
-As you maybe already noticed we have two different clients, one is WinX UWP and the other one Mobile, which is used to develop clients for three different platforms namely iOS, Android and Windows (-> it doesn’t really differentiate from the previously mentioned UWP except it’s developed in a different framework which is Maui in this case). The customizing stays the same in case of the syntax, but there are some differences in the naming of controls and attributes. Unfortunately, there is no decent documentation of these differences, but the Microsoft documentation and, in general, the internet can support you when searching e.g. for a control in Maui that you used in UWP.
+As you maybe already noticed we have two different clients, one is WinX UWP and the other one Mobile, which is used to develop clients for three different platforms namely iOS, Android and Windows (-> it doesn’t really differentiate from the previously mentioned UWP except it’s developed in a different framework which is Maui in this case). The customizing stays the same in case of the syntax, but there are some differences in the naming of controls and attributes. Unfortunately, there is no decent documentation of these differences, but the Microsoft documentation and, in general, the internet can support you when searching e.g. for a control in Mobile that you used in UWP.
 More specific documentations about Mobile Customizing can be found under [[Mobile XAML]].