Search -> filter (refactor), array -> (multi)Row(s)

Front end
========
- ObjectArray -> MultiRow: refactor search -> filter
- MultiInput: currentTime reactive

Back End
=======
- Module: execOnUpdate() and update() from state to service to check for originID for saveNeeded, array to rows
- Devices, tasks: property -> control, use ModuleState::update
- IO: add Cube202010
- E_MoonLight: random speed->fade

Author: ewowi

docs/develop/modules.md

@@ -39,28 +39,28 @@ ModuleDemo(PsychicHttpServer *server
 
 ```cpp
 void setupDefinition(JsonArray root) override{
-    JsonObject property; // state.data has one or more properties
-    JsonArray details; // if a property is an array, this is the details of the array
-    JsonArray values; // if a property is a select, this is the values of the select
+    JsonObject control; // state.data has one or more properties
+    JsonArray details; // if a control is an array, this is the details of the array
+    JsonArray values; // if a control is a select, this is the values of the select
 
-    property = root.add<JsonObject>(); property["name"] = "hostName"; property["type"] = "text"; property["default"] = "MoonLight";
-    property = root.add<JsonObject>(); property["name"] = "connectionMode"; property["type"] = "select"; property["default"] = "Signal Strength"; values = property["values"].to<JsonArray>();
+    control = root.add<JsonObject>(); control["name"] = "hostName"; control["type"] = "text"; control["default"] = "MoonLight";
+    control = root.add<JsonObject>(); control["name"] = "connectionMode"; control["type"] = "select"; control["default"] = "Signal Strength"; values = control["values"].to<JsonArray>();
     values.add("Offline");
     values.add("Signal Strength");
     values.add("Priority");
 
-    property = root.add<JsonObject>(); property["name"] = "savedNetworks"; property["type"] = "array"; details = property["n"].to<JsonArray>();
+    control = root.add<JsonObject>(); control["name"] = "savedNetworks"; control["type"] = "rows"; details = control["n"].to<JsonArray>();
     {
-        property = details.add<JsonObject>(); property["name"] = "SSID"; property["type"] = "text"; property["default"] = "ewtr"; property["min"] = 3; property["max"] = 32; 
-        property = details.add<JsonObject>(); property["name"] = "Password"; property["type"] = "password"; property["default"] = "";
+        control = details.add<JsonObject>(); control["name"] = "SSID"; control["type"] = "text"; control["default"] = "ewtr"; control["min"] = 3; control["max"] = 32; 
+        control = details.add<JsonObject>(); control["name"] = "Password"; control["type"] = "password"; control["default"] = "";
     }
 
 }
 
 ```
 
 * Implement function **onUpdate** to define what happens if data changes
-    * struct UpdatedItem defines the update (parent property (including index in case of multiple records), name of property and value)
+    * struct UpdatedItem defines the update (parent control (including index in case of multiple records), name of control and value)
     * This runs in the httpd / webserver task. To run it in another task (application task) use runInAppTask - see [ModuleLightsControl](https://github.com/MoonModules/MoonLight/blob/main/src/MoonLight/ModuleLightsControl.h)
 
 ```cpp
@@ -131,7 +131,7 @@ submenu: [
 
 ### Readonly data
 
-A module can consist of data which is edited by the user (e.g. selecting a live script to run) and data which is send from the server to the UI (e.g. a list of running processes). Currently both type of valuas are stored in state data and definition. Distinguished by property["ro"] = true in setupDefinition. So the client uses state data and definition to build a screen with both types visually mixed together (what is desirable). Currently there are 2 websocket events: one for the entire state (including readonly) and one only for readonly which only contains the changed values. Module.svelte handles readonly differently by the function handleRO which calls updateRecursive which only update the parts of the data which has changed.
+A module can consist of data which is edited by the user (e.g. selecting a live script to run) and data which is send from the server to the UI (e.g. a list of running processes). Currently both type of values are stored in state data and definition. Distinguished by control["ro"] = true in setupDefinition. So the client uses state data and definition to build a screen with both types visually mixed together (what is desirable). Currently there are 2 websocket events: one for the entire state (including readonly) and one only for readonly which only contains the changed values. Module.svelte handles readonly differently by the function handleRO which calls updateRecursive which only update the parts of the data which has changed.
 
 It might be arguable that readonly variables are not stored in state data.
 

interface/src/lib/components/moonbase/EditObject.svelte

@@ -6,7 +6,7 @@
 	import Cancel from '~icons/tabler/x';
 
 	import MultiInput from '$lib/components/moonbase/MultiInput.svelte';
-	import ObjectArray from '$lib/components/moonbase/ObjectArray.svelte';
+	import MultiRow from '$src/lib/components/moonbase/MultiRow.svelte';
 
 	interface Props {
 		property: any;
@@ -51,13 +51,13 @@
 			{#each property.n as propertyN}
 				{#if propertyN.type == 'array'}
 					<label for={propertyN.name}>{propertyN.name}</label>
-					<ObjectArray
+					<MultiRow
 						property={propertyN}
 						bind:data={dataEditable}
 						definition={localDefinition}
 						{onChange}
 						{changeOnInput}
-					></ObjectArray>
+					></MultiRow>
 				{:else if propertyN.type == 'controls'}
 					{#each dataEditable[propertyN.name] as control}
 						<!-- e.g. dE["controls"] -> {"name":"xFrequency","type":"slider","default":64,"p":1070417419,"value":64} -->