XAML - Revision history

KGR: /* Properties */

2026-04-28T08:51:24Z

‎Properties

KGR: /* PropertyByName[MP_PROPERTY]... */

2026-04-28T07:35:14Z

‎PropertyByName[MP_PROPERTY]...

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

@@ Line 313: / Line 313: @@
 ! Collection !! {{Tooltip|Performance|Could rendering be slowed down by using this binding, especially on ItemTemplates used in a list of many items.}} !! {{Tooltip|Capability|Extent of the viewmodel accessed}} !! {{Tooltip|Lazy-Loaded|Loaded on-demand (vs. always present)}}
 |-
-| Values || Great || Very limited - Read only, Property value only || No
+| Values || Great || Very limited - Read only, Property (or [[Traits]] {{Version/WinXSince|5.1}}{{Version/MobileSince|5.1}}) value only || No
 |-
 | PropertyItems || Good || Limited - Read only || No
@@ Line 323: / Line 323: @@
 |}
-==== Values[MP_PROPERTY] ====
+==== Values[NAME] ====
 * This is the most basic and performant way to bind to a property value.
 * This collection simply displays the 'true' value of a property, meaning that it is only useful displaying for simple properties, such as String, Int, Dbl, unformatted DateTime, etc. Properties that have a DisplayValue that is different from their true value, such as GUIDs or selective list items with labels, are not best displayed using this binding.
-* For complex iproperties, it can be still be used in the xaml for non-display purposes, such as in combination with converters or commands. It is immediately present on the most basic content viewmodel (the ContentListItemViewModels used by child lists) without having to be loaded, and remains the best choice in most cases.
+* For complex properties, it can be still be used in the xaml for non-display purposes, such as in combination with converters or commands. It is immediately present on the most basic content viewmodel (the ContentListItemViewModels used by child lists) without having to be loaded, and remains the best choice in most cases.
 <tabs>
@@ Line 336: / Line 337: @@
 <tab name="Instead do">
 <source lang = "XML">
-Command="{Binding NavigateToGuidCommand}" Command Parameter="{Binding Values[MP_GUID]}"
+Command="{Binding NavigateToGuidCommand}" Command Parameter="{Binding Values[GUID]}"
 </source>
 </tab>
@@ Line 355: / Line 356: @@
 {{Hint|The Values[ ] collection delivers the property's value as a string. The equivalent for the other bindings (above shown as '...') is <code>{Binding Collection[PROPERTY_NAME].'''DisplayValue'''}</code>, however, the capability of these viewmodels goes far beyond the DisplayValue. Use [[Developer_Mode]] to learn more.}}
-[[Category:Mobile|XAML]]
-[[Category:WinX|XAML]]
-[[Category:XAML|XAML]]
 ==== * Troubleshooting null property values ====
@@ Line 375: / Line 376: @@
 * The [[XAML_Tips#SetPropertyValueCommand|Set Property Value Command]] sets a named property to a specific or calculated (such as through an [[EvalExpression]]) value.
+[[Category:Mobile|XAML]]
+[[Category:WinX|XAML]]
 == Commands ==

@@ Line 350: / Line 350: @@
 * "Properties.XItems" is not a real collection. The most frequently used collections are Properties.AllItems, Properties.VisibleItems, Properties.EditableItems, and Properties.ImportantItems (properties which fall into the [[UBIK_WinX_Client_Basics#High_priority_properties|Priority threshold]]). The number of properties delivered to a content object in each collection (for example; all, 80%, 40% and 10%, respectively) is also a consideration when estimating the performance impact of binding to these collections; simply put, use the smallest collection possible where the desired property is consistently located.
-==== PropertyByName[MP_PROPERTY]... ====
+==== PropertyByName[MP_PROPERTY] ====
 This collection was created to overcome the performance impact arising from using Properties.XItems, by individually loading the PropertyViewModel for the named property. However, note that the benefit only lasts while the binding is used sparingly; rendering performance will be roughly the same as loading the Properties collection after 3-5 uses on a single item template.
 {{Hint|The Values[ ] collection delivers the property's value as a string. The equivalent for the other bindings (above shown as '...') is <code>{Binding Collection[PROPERTY_NAME].'''DisplayValue'''}</code>, however, the capability of these viewmodels goes far beyond the DisplayValue. Use [[Developer_Mode]] to learn more.}}
 ==== * Troubleshooting null property values ====

@@ 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 ==