Traits - Revision history

LGE: /* 3. Values (Raw Data) */

2026-07-03T09:59:37Z

‎3. Values (Raw Data)

2026-04-28T08:55:28Z

2026-04-28T08:53:09Z

‎SetValueCommand

2026-04-28T08:47:00Z

2026-04-28T08:29:47Z

2026-04-28T08:12:59Z

‎SetValueCommand

2026-04-28T08:06:59Z

‎SetValueCommand

2026-04-28T08:03:41Z

2026-04-28T07:52:07Z

‎Traits

2026-04-28T06:48:06Z

@@ Line 42: / Line 42: @@
 === 3. Values (Raw Data) ===
-See [[XAML#Values.5BMP_PROPERTY.5D|Values]]
+See [[XAML#Values.5BNAME.5D|Values]]
 ----
 == Commands (Set & Create Values) ==

@@ Line 58: / Line 58: @@
 <syntaxhighlight lang="xml">
 <Button Command="{Binding SetValueCommand}" Text="Set">
      <Button.CommandParameter>

@@ Line 42: / Line 42: @@
 === 3. Values (Raw Data) ===
-This is a combined getter that returns the raw value directly from the dictionary, instead of providing a complex <code>TraitViewModel</code> or <code>PropertyViewModel</code>.
+See [[XAML#Values.5BMP_PROPERTY.5D|Values]]
-* '''Usage:''' For pure display purposes or evaluations.
-−
-'''XAML Example (Reading raw data):'''
-<syntaxhighlight lang="xml">
-<Entry Text="{Binding Values[NAME]}" />
-</syntaxhighlight>
-''(Replace NAME with the placeholder of your actual trait or property name)''
 ----

← Older revision		Revision as of 08:29, 28 April 2026
Line 4:		Line 4:

	This feature is particularly useful for data that only becomes known at runtime or varies significantly from instance to instance. Please note that traits do not use lazy loading, making them act rather "heavy weight" from a user's perspective.		This feature is particularly useful for data that only becomes known at runtime or varies significantly from instance to instance. Please note that traits do not use lazy loading, making them act rather "heavy weight" from a user's perspective.
		+
		+	Supported types:
		+	* int
		+	* double
		+	* string
		+	* bool
		+	* date time

	{{Attention\|This feature must be used wisely, too many traits could impact the performance. Traits do not replace properties.}}		{{Attention\|This feature must be used wisely, too many traits could impact the performance. Traits do not replace properties.}}

@@ Line 50: / Line 50: @@
 === SetValueCommand ===
 This command on the <code>ContentViewModel</code> orchestrates value assignments and handles the '''creation of new traits''' if necessary.
-* '''If the trait exists:''' The value will be overwritten.
+* '''If a trait exists:''' The value will be overwritten.
-* '''If a property exists:''' The property's value will be overwritten (if it is not locked/read-only).
+* '''If a editable property exists:''' The property's value will be overwritten (if it is not locked/read-only).
-* '''If neither exists:''' A trait is added to the {{UBIK}} content.
+* '''Otherwise:''' A trait is added to the {{UBIK}} content.
 '''XAML Example (Setting a value):'''

@@ Line 67: / Line 67: @@
 </Button>
 </syntaxhighlight>
-''(Note: Customizers can replace the static string placeholders with dynamic bindings to controls like Entry or DatePicker as needed)''
+''(Note: Replace MY_TRAIT_NAME & MY_TRAIT_VALUE with the placeholder of your actual trait or property name/value)''
 ----

@@ Line 20: / Line 20: @@
 '''XAML Example (Reading a value):'''
 <syntaxhighlight lang="xml">
-<Entry Text="{Binding ValueAccessors[NAME]}" />
+<Entry Text="{Binding ValueAccessors[NAME].Value}" />
 </syntaxhighlight>
 ''(Replace NAME with the placeholder of your actual trait or property name)''
@@ Line 30: / Line 30: @@
 '''XAML Example (Reading only Trait):'''
 <syntaxhighlight lang="xml">
-<Entry Text="{Binding TraitByName[TRAIT_NAME]}" />
+<Entry Text="{Binding TraitByName[TRAIT_NAME].Value}" />
 </syntaxhighlight>
 ''(Replace TRAIT_NAME with the placeholder of your actual trait)''
@@ Line 62: / Line 62: @@
          <classes:KeyValueList>
              <classes:KeyValueParameter Key="Name" Value="MY_TRAIT_NAME" />
-             <classes:KeyValueParameter Key="Value" Value="My Trait Value" />
+             <classes:KeyValueParameter Key="Value" Value="MY_TRAIT_VALUE" />
          </classes:KeyValueList>
      </Button.CommandParameter>

@@ Line 13: / Line 13: @@
 The <code>ValueAccessors</code> acts as a combined dynamic value resolver. It provides a built-in fallback logic:
 # '''Trait Lookup:''' First attempts to resolve the value via a trait with the specified name.
-# '''Property Fallback:''' If no trait is found, it queries a regular {{UBIK}} Property with that name (see [[PropertyByName]]).
+# '''Property Fallback:''' If no trait is found, it queries a regular {{UBIK}} Property with that name (see [[XAML#PropertyByName.5BMP_PROPERTY.5D|PropertyByName]]).
 # '''Default:''' If neither exists, it returns <code>null</code>.