1

Allow us to copy unreferenced variables into specific projects

Sometimes I have variables that for whatever reason might not be referenced anywhere AS FAR AS TASKER KNOWS.

It is possible their references are formed programmatically, for example, and still being used in a project.

Without the explicit reference, Tasker places the variable into the home folder.  It can't be placed into the folders where it's being programmatically summoned.

I understand that I COULD create inane tasks in that project that reference these variables in the project they're used, but that adds task clutter to my increasingly bloated task list.  It would be cleaner to just be able to add these variables to that project without needing to create useless tasks.

Without the ability to copy a variable into a project, I am forced to navigate back to the home folder whenever I want to check it, and then back to the project I'm working on.  It's rather disorienting.

1 reply

To resolve this issue, I make a dummy action at the end of tasks which use a global variable programmatically, such that Tasker can't "see" it. This action refers to the variable, e.g. "Variable set %dummy to %VAR", but the action is disabled. This causes the variable to show in the project like you want it to. If there are more than one you can just list them all in the same action, no need to create multiple actions. This way the "clutter" can be as little as one action per project.