Put the reason why the event occurred in the event parameters. I'd like to customize my Monitor task for the various reasons this event occurs; phone boot up, Tasker enabled, new version of Tasker installed, system update, etc.
Hi. Not sure what you mean. Why aren't you able to do that now?
I'm trying to use it now, but most events don't seem to use %evtprm, the variables aren't set.
%evtprm() corresponds to the input variables of each event. If there aren't any inputs in the event then that array won't have any values. Which values do you need that aren't available? Could you give me an example?
I didn't realize that they corresponded to input variables.
My actual request is for some of the events that have no inputs. For example, the Monitor Start event. What I'd really like ito know is why the event occurred. There are several reasons, Device Boot event, user selecting Enable Tasker, new version of Tasker installed and a Tasker error. I have a task that is initiated by the Monitor Start event and want to have it respond appropriately to the event.
Oh I see. Thanks for clarifying.
I not really looking for values in %evtprm. What I'd like is a variable that shows why the monotor evenr occured. Currently I can use a notification to see that a new version of Tasker has been installed or if a reboot event occured. I can't tell if Tasker was disabled and reenabled or if a Tasker error occured. It would be great to have a status variable as part of the Monitor event that shows the reason why the Monitor event occured.
