1
Solved

Testing if indirectly referenced variable is set generates error in the Tasker editor; Workround given.

With the following task, if lines three to five are not deactivated, then the error shown below will pop up when the tasker editor is started, if you edit the task. That is, just open up the task, don't change it, close it, close the tasker editor, open the tasker editor and the error dialogue shown will pop up. There is no need to run the task to get the error message. Lines three to five actualy work fine, you just get an error message every time you edit the task.

Fortunately I have discovered a work around which is show in the remainder of the task.

A1: Variable Set [ Name:%fred To:Flintstone Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 ]
A2: Variable Set [ Name:%lookup To:fred Recurse Variables:Off Do Maths:Off Append:Off Max Rounding Digits:3 ]
A3: [X] If [ %%lookup Set ]
A4: [X] Flash [ Text:%%lookup Long:Off ]
A5: [X] End If
A6: Write File [ File:Tasker/javascript/temp.js Text:var testa = %lookup; var testb = %lookup; Append:Off Add Newline:Off ]
A7: JavaScript [ Path:Tasker/javascript/temp.js Libraries: Auto Exit:On Timeout (Seconds):45 ]
A8: If [ %testa eq %testb ]
A9: Flash [ Text:%lookup is set. Long:Off ]
A10: Else
A11: Flash [ Text:%lookup is not set. Long:Off ]
A12: End If

2 replies

Hi there, thanks for the report! Can you please try this version? https://drive.google.com/file/d/1clW433pxvypJQM0QhuKyIk0pmTC7Hccx/view?usp=sharing

I have found the workround does not work sometimes. However I have realised that I can use Test Tasker local variables as a work round.

Topic is closed for comments