Property Direct Edit (Client) - Revision history

KGR: /* PropertyViewModel */

2026-05-07T12:57:40Z

‎PropertyViewModel

CWI at 13:23, 23 September 2025

2025-09-23T13:23:49Z

CWI at 07:29, 23 September 2025

2025-09-23T07:29:55Z

CWI at 07:40, 22 September 2025

2025-09-22T07:40:58Z

CWI at 10:25, 18 September 2025

2025-09-18T10:25:37Z

LKR: /* Supported property types */

2024-03-05T06:38:23Z

‎Supported property types

LKR: /* Supported property types */

2024-03-05T06:37:33Z

‎Supported property types

LGE: /* PropertyViewModel */

2023-06-16T13:04:38Z

‎PropertyViewModel

LGE: /* PropertyViewModel */

2023-04-20T13:45:07Z

‎PropertyViewModel

LGE: /* Supported property types */

2022-06-22T07:45:22Z

‎Supported property types

@@ Line 48: / Line 48: @@
 This is the view model for every single {{UBIK}} property and also the basement for property direct editing (and regular editing alike). For example, a certain named PropertyViewModel (with the name of PROPERTY_NAME) of the context object in a content page is accessible as <code>{Binding Properties.VisibleItems[PROPERTY_NAME]}</code>.
-[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_NotInEditing.png|thumb|A test template for direct editing a String property (Mobile)]]
+[[File:UBIK_DirectEditing.png|thumb|A test template for direct editing a String property (Mobile)]]
-[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_InEditing.png|thumb|The same template now in edit mode (Mobile)]]
 In the example demonstrated in the screenshot where a test template is used to enable direct editing of a String/Text typed property, the following members of the PropertyViewModel are involved.
 * '''InEditing''': This is the boolean member indicating whether the PropertyViewModel is currently in edit mode. It can be used to decide whether the UI should display the DisplayValue text or present a text box for user input;
@@ Line 136: / Line 135: @@
 {{Hint|If you are unsure whether '''ValueItem.PropertyValue''' or '''ValueItem.PropertyValueSessionless''' should be used for a certain property type, go with the former. Because most types do have sessions in their direct editing UI. Also, the problem of misusing the former can be seen immediately, namely the editing doesn't work, whereas misusing the latter can lead to more issues that are hard to notice at first.}}
+[[Category:Client|Property Direct Edit (Client)]]
+[[Category:Mobile|Property Direct Edit (Client)]]
+[[Category:Version 4.0|Property Direct Edit (Client)]]
+[[Category:WinX|Property Direct Edit (Client)]]
 == Relevant types ==

← Older revision		Revision as of 13:23, 23 September 2025
Line 266:		Line 266:
	[[Category:Version 4.0\|Property Direct Edit (Client)]]		[[Category:Version 4.0\|Property Direct Edit (Client)]]
	[[Category:WinX\|Property Direct Edit (Client)]]		[[Category:WinX\|Property Direct Edit (Client)]]
−	~~[[Category:Version 5.0\|Property Direct Edit (Client)]]~~

← Older revision		Revision as of 07:29, 23 September 2025
Line 266:		Line 266:
	[[Category:Version 4.0\|Property Direct Edit (Client)]]		[[Category:Version 4.0\|Property Direct Edit (Client)]]
	[[Category:WinX\|Property Direct Edit (Client)]]		[[Category:WinX\|Property Direct Edit (Client)]]
		+	[[Category:Version 5.0\|Property Direct Edit (Client)]]

@@ Line 11: / Line 11: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 They are accessible as DataTemplates from UBIKThemes.xamlx and the syntax in XAML is <code>{DynamicResource TEMPLATE_NAME}</code>. Just like such templates, they can be customized by providing your own DataTemplate resources (with the keys of TEMPLATE_NAME) in UBIKThemes.xamlx.
 </tab>
@@ Line 26: / Line 26: @@
 * With selective list items: named as UBIKPropertyDirectItemList.
-{{Hint|Due to the limited screen size of most mobile devices, direct editing is not enabled by default in the Xamarin clients.}}
+{{Hint|Due to the limited screen size of most mobile devices, direct editing is not enabled by default in the Mobile clients.}}
 === For MRO-Tasks: ===
@@ Line 38: / Line 38: @@
 * With selective list items: named as UBIKTaskPropertyList.
-{{Hint|Due to the limited screen size of most mobile devices, direct editing is not enabled by default for DateTime and GeoData types in the Xamarin clients.}}
+{{Hint|Due to the limited screen size of most mobile devices, direct editing is not enabled by default for DateTime and GeoData types in the Mobile clients.}}
@@ Line 48: / Line 48: @@
 This is the view model for every single {{UBIK}} property and also the basement for property direct editing (and regular editing alike). For example, a certain named PropertyViewModel (with the name of PROPERTY_NAME) of the context object in a content page is accessible as <code>{Binding Properties.VisibleItems[PROPERTY_NAME]}</code>.
-[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_NotInEditing.png|thumb|A test template for direct editing a String property (Xamarin)]]
+[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_NotInEditing.png|thumb|A test template for direct editing a String property (Mobile)]]
-[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_InEditing.png|thumb|The same template now in edit mode (Xamarin)]]
+[[File:UBIK_Xamarin_UI_Template_PropertyDirectItemString_Debug_InEditing.png|thumb|The same template now in edit mode (Mobile)]]
 In the example demonstrated in the screenshot where a test template is used to enable direct editing of a String/Text typed property, the following members of the PropertyViewModel are involved.
 * '''InEditing''': This is the boolean member indicating whether the PropertyViewModel is currently in edit mode. It can be used to decide whether the UI should display the DisplayValue text or present a text box for user input;
@@ Line 73: / Line 73: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 <source lang = "xml">
    <Button ...
@@ Line 106: / Line 106: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 <source lang = "xml">
    <Button ...
@@ Line 155: / Line 155: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 Namespace <code>xmlns:resources="clr-namespace:UBIK.CPL.Resources;assembly=UBIK.CPL"</code>
 </tab>
@@ Line 171: / Line 171: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 Namespace <code>xmlns:resources="clr-namespace:UBIK.CPL.Resources;assembly=UBIK.CPL"</code>
 </tab>
@@ Line 208: / Line 208: @@
 </tab>
-<tab name="Xamarin">
+<tab name="Mobile(Xamarin)">
 The SelectAllEntry optionally accepts two commands (ReturnCommand & EscapeCommand) to execute when a user inputs the return key {{key press|Enter}} and the escape key {{key press|Esc}} respecitively.
 <source lang = "xml">
@@ Line 245: / Line 245: @@
 </tab>
-<tab name="DateTimeControl Xamarin">
+<tab name="DateTimeControl Mobile(Xamarin)">
 The CalendarControl has an additional Event called "DateSelected" that is called when confirming a value on the flyoutpickers. The TimeControl has a similar "TimeSelected" Event (Note that this event may have wrong behaviour on iOS)
 <source lang = "xml">
@@ Line 263: / Line 263: @@
 [[Category:Client|Property Direct Edit (Client)]]
 [[Category:Version 4.0|Property Direct Edit (Client)]]
 [[Category:WinX|Property Direct Edit (Client)]]

@@ Line 40: / Line 40: @@
 {{Hint|Due to the limited screen size of most mobile devices, direct editing is not enabled by default for DateTime and GeoData types in the Xamarin clients.}}
-[[Category:Client|Property Direct Edit (Client)]]
-[[Category:Version 4.0|Property Direct Edit (Client)]]
-[[Category:WinX|Property Direct Edit (Client)]]
-[[Category:Xamarin|Property Direct Edit (Client)]]
 == PropertyViewModel ==
@@ Line 136: / Line 136: @@
 {{Hint|If you are unsure whether '''ValueItem.PropertyValue''' or '''ValueItem.PropertyValueSessionless''' should be used for a certain property type, go with the former. Because most types do have sessions in their direct editing UI. Also, the problem of misusing the former can be seen immediately, namely the editing doesn't work, whereas misusing the latter can lead to more issues that are hard to notice at first.}}
-[[Category:Client|Property Direct Edit (Client)]]
-[[Category:Version 4.0|Property Direct Edit (Client)]]
-[[Category:WinX|Property Direct Edit (Client)]]
-[[Category:Xamarin|Property Direct Edit (Client)]]
 == Relevant types ==
@@ Line 265: / Line 265: @@
 [[Category:Version 4.0|Property Direct Edit (Client)]]
 [[Category:WinX|Property Direct Edit (Client)]]
-[[Category:Xamarin|Property Direct Edit (Client)]]
+[[Category:Mobile|Property Direct Edit (Client)]]

@@ Line 5: / Line 5: @@
 == Supported property types ==
-In {{UBIK}}, we provide default templates for some most frequently used property types. However, you can use your own templates, controls, etc. as you like to deal with these property types or even more (as long as you can find suitable UI controls for dealing with these types).
+In {{UBIK}}, we provide default templates for some most frequently used property types. However, you can use your own templates, controls, etc. as you like to deal with these property types or even more (as long as you can find suitable UI controls for dealing with these types). Direct editing properties also support [[Min Max Properties]].
 <tabs>
 <tab name="UWP">
-They are accessible as DataTemplates from UBIKThemes.xaml (use the [[Developer_Mode]] to find the default copy) and the syntax in XAML is <code>{StaticResource TEMPLATE_NAME}</code>. Just like other such templates, they can be customized by overriding the DataTemplates with respective keys in UBIKThemes.xaml. Direct editing properties also supports [[Min Max Properties]].
+They are accessible as DataTemplates from UBIKThemes.xaml (use the [[Developer_Mode]] to find the default copy) and the syntax in XAML is <code>{StaticResource TEMPLATE_NAME}</code>. Just like other such templates, they can be customized by overriding the DataTemplates with respective keys in UBIKThemes.xaml.
 </tab>

← Older revision		Revision as of 13:04, 16 June 2023
Line 124:		Line 124:

	{{Hint\|Once again, you can use the [[Developer_Mode]] to find out more about the PropertyViewModel, like where they are available and how they can be accessed in XAML, or what other members are available underneath, etc.}}		{{Hint\|Once again, you can use the [[Developer_Mode]] to find out more about the PropertyViewModel, like where they are available and how they can be accessed in XAML, or what other members are available underneath, etc.}}
		+
		+	=== ValueItem.PropertyValue or ValueItem.PropertyValueSessionless {{Version/WinXSince\|4.4}}{{Version/XamarinSince\|4.4}} ===
		+	When it comes to property editing, there's the concept of edit sessions. A property editor always entails a session which starts when the editor is opened and ends when the editor is closed.
		+	However, this could be different in direct editing. For example,
		+	* The standard UI in {{UBIK}} for direct string editing still has sessions. The session starts when you click on the displayed value text and it turns into a text box for value input. It ends when you confirm the input value and the text box turns back into the displayed value text.
		+	* On the other hand, the direct boolean editing is, for example, sessionless. This is because the UI displays a check box the entire time and there's no way to tell the start or the end of a session.
		+
		+
		+	For most value types (e.g. where typing is involved during direct editing), the session concept still applies. '''ValueItem.PropertyValue''' should be used in bindings in such cases. Otherwise, the input values might be lost during editing. In other cases where direct editing is sessionless, '''ValueItem.PropertyValueSessionless''' should be used. Otherwise, the input value will be rejected since the property is technically speaking not in any edit session.
		+
		+	{{Hint\|If you are unsure whether '''ValueItem.PropertyValue''' or '''ValueItem.PropertyValueSessionless''' should be used for a certain property type, go with the former. Because most types do have sessions in their direct editing UI. Also, the problem of misusing the former can be seen immediately, namely the editing doesn't work, whereas misusing the latter can lead to more issues that are hard to notice at first.}}

	[[Category:Client\|Property Direct Edit (Client)]]		[[Category:Client\|Property Direct Edit (Client)]]

@@ Line 55: / Line 55: @@
 * '''ValueItem.PropertyValue''': This is the value of property stored at the PropertyViewModel which can differ from the underlying property value because there can be editing changes not yet confirmed/saved. It can be read from and written to by the text box;
 * '''DisplayValue''': This is the textual version of ValueItem.PropertyValue used for displaying when the InEditing is false;
-* '''StartDirectEditCommand''': Sets InEdit to true and starts the direct editing session. In the example, this is linked to the tapped event of the entire template area;
+* '''StartDirectEditCommand''': Sets InEditing to true and starts the direct editing session. In the example, this is linked to the tapped event of the entire template area;
-* '''ConfirmEditCommand''': Confirms the edit and sets InEdit to false. Even if the property value is not changed, this will give the property a new validation timestamp, technically modifying the property;
+* '''ConfirmEditCommand''': Confirms the edit and sets InEditing to false. Even if the property value is not changed, this will give the property a new validation timestamp, technically modifying the property;
 <tabs>
 Optional command parameter for ConfirmEditCommand: ToValidate - Whether a validation timestamp should be added even if the value is unchanged when confirmed. Defaults to true if unspecified.