Are these functions of Tasker "ignored" by you?

This paper aims to share some little-known functions with Tasker users, so that more people can use them flexibly when writing configurations. Although these functions are also mentioned in the Tasker User Guide, most Tasker users have not learned about them, and I think some advanced users of Tasker may not be clear about them. In fact, don't underestimate these unpopular functions. Through them, we can easily meet our own needs.

Tasker users who have used the conditional judgment function know ~R/! The matching type of ~R operator is regular expression, and it is also known that it can be used in the If condition and state condition "variable value" of action.

Since version 5.0, Tasker has added a function, "Where simple matching is possible, just add ~R or! ~R, it will become a regular expression match. "

%evtprm is a local array variable that is passed to the "Entry" task after the event condition is triggered. I believe many people have come into contact with it, but how to quickly determine the meaning of each element in the %evtprm array, I think, should only be known by a few people. For example, when the event notified by WeChat is triggered, can you quickly determine whether the variable representing the notification content is %evtprm2 or %evtprm3?

There is a saying in the Tasker User Guide, "The order of% evtprm array elements is consistent with the order of event parameters (items)", which means the following figure:

From this, we can quickly know that %evtprm2 and %evtprm3 represent the title and content of the notice respectively.

The following is a description of variable reference (extracted from the variable part of Tasker Chinese User Guide translated by myself).

There is a class of local variables in the action "test Tasker", which can be used to store all assigned local variables in the running task (before the action is executed), as shown in the following figure:

This function can play an auxiliary role in configuration preparation. For example, I want to know the variable name of an extra parameter of a receiving intention to be used in the preparation of the task, and I can get it by this method (from the above figure, %newrssi is an extra parameter with intention).

Recursive variables are optional parameters of the action "Variable Set" (the item selected in the following figure).

Its function is to recursively replace all assignment variables, and the effect is shown in the following example: