This function is intended to create Actions in a Module with code. This functionality is used by many Modules to enable automatic creation of the required Actions.

There are 3 different “dynamicRebuild” functions:

null dynamicRebuild(string deviceName,string jsonDescription,string folder)
null dynamicRebuildFromDescription(string jsonDescription,string folder,string namePattern)
null dynamicRebuildFromJsonDescription(string deviceName,string jsonDescription,string folder)

dynamicRebuildFromDescriptions(string jsonDescription,string folder,string namePattern)

In this example, we are working with a template written in JSON format. This is modified in the code to create the different code in the Actions and with self().dynamicRebuildFromDescriptions.

The Module used for this example is “EventScheduler” Version 1.5, More precisely, the “createEvents()” Action holds this functionality.

string jsonDescription

The code after the template modifies the template and changes the string in the body accordingly. 

To see how these templates can look like, it is easiest to open a PIXERA Module in its JSON format, so you can see the syntax and possibilities directly:

--json template for new events
local myTemplate = [[
	{
		"name": "Event_##IDX##",
		"kind": "fn",
		"attKind": "standard",
		"slotStyle": "leftIn;rightOut",
		"params": [
			{
				"name": "val",
				"type": "string"
			},
			{
				"name": "doSet",
				"type": "bool"
			}
		],
		"result": {
		},
		"body": "if val ~= nil then;self.eventVal##IDX## = val \n pixc.suppressCallRefs() \n pixc.report(self.eventVal##IDX##) \n return self.eventVal##IDX## \n end \n pixc.report(self.eventVal##IDX##) \n pixc.callRefs(self.eventVal##IDX##) \n return self.eventVal##IDX##"
	}
]]

--modify strings in template
local ActionList = '['
local removeLast = false
local vEnd = self.helper:getProperty("Number of Events")

for i= 1, vEnd,1 do
	local tmod = myTemplate
	local s = tostring(i)
	removeLast = true
	local c;

	tmod, c = string.gsub(tmod,"##IDX##", s)
	ActionList = ActionList..tmod;
	ActionList = ActionList..','
end

if removeLast == true then
	ActionList = ActionList:sub(1, -2)
end
ActionList = ActionList..']'
--adding funktions to this Module:
self().dynamicRebuildFromDescriptions(ActionList, "Events", "(.*)")

The variable “ActionList” corresponds to the specified templates that have been modified by the code.

string folder

The string "Events" refers to the folder in which the Actions are generated.

If an empty string is passed here, they are generated without a folder. It is possible to leave this empty and specify an element in the JSON template: "subPath": "Events". 

With this functionality, it is possible to create Actions in different folders:

local myTemplate = [[
	{
		"name": "Event_##IDX##",
		"subPath": "Events",
		"kind": "fn",
		"attKind": "standard",
		"slotStyle": "leftIn;rightOut",
		"params": [
			{
				"name": "val",
				"type": "string"
			},
			{
				"name": "doSet",
				"type": "bool"
			}
		],
		"result": {
		},
		"body": "if val ~= nil then;self.eventVal##IDX## = val \n pixc.suppressCallRefs() \n pixc.report(self.eventVal##IDX##) \n return self.eventVal##IDX## \n end \n pixc.report(self.eventVal##IDX##) \n pixc.callRefs(self.eventVal##IDX##) \n return self.eventVal##IDX##"
	}
]]

string namePattern

The “namePattern” is there to find Modules that already exist and not to regenerate them again.

This is passed as a string, Regex is used here.

• . - a "dot" indicates any character
• * - means “0 or more instances of the preceding regex token”

In this example, we use “(.*)” to filter for the same names, and not create an Action twice.

dynamicRebuildFromJsonDescription(string deviceName,string jsonDescription,string folder)

This function can be accessed via the API. The Module in which the Action is to be generated can be specified here:

string deviceName

The name of the Module in which the Actions are to be generated must be entered here.

string jsonDescription

Behaves in exactly the same way as in dynamicRebuildFromDescriptions.

string folder

Behaves in exactly the same way as in dynamicRebuildFromDescriptions.

Example:

--json template for new events
local myTemplate = [[
	{
		"name": "Event_##IDX##",
		"kind": "fn",
		"attKind": "standard",
		"slotStyle": "leftIn;rightOut",
		"params": [
			{
				"name": "val",
				"type": "string"
			},
			{
				"name": "doSet",
				"type": "bool"
			}
		],
		"result": {
		},
		"body": "if val ~= nil then;self.eventVal##IDX## = val \n pixc.suppressCallRefs() \n pixc.report(self.eventVal##IDX##) \n return self.eventVal##IDX## \n end \n pixc.report(self.eventVal##IDX##) \n pixc.callRefs(self.eventVal##IDX##) \n return self.eventVal##IDX##"
	}
]]

--modify strings in template
local ActionList = '['
local removeLast = false
local vEnd = 3

for i= 1, vEnd,1 do
	local tmod = myTemplate
	local s = tostring(i)
	removeLast = true
	local c;

	tmod, c = string.gsub(tmod,"##IDX##", s)
	ActionList = ActionList..tmod;
	ActionList = ActionList..','
end

if removeLast == true then
	ActionList = ActionList:sub(1, -2)
end

--adding funktions to Module:
PIXERA.Utility.dynamicRebuildFromJsonDescription("Module2", ActionList,"")

This Action now creates 3 Actions in Module2

local json = '[ {"name": ""} ]'
self().dynamicRebuildFromDescriptions(json, "", "(.*)")

PIXERA 1.9.222 | 11. December 2023