Difference between revisions of "Triggers"
(Improve explanations) Tags: Mobile web edit Mobile edit |
|||
| Line 3: | Line 3: | ||
For a trigger to fire, the macro must be available (i.e. ready to run, not disabled) at the exact time the event occurs. Otherwise, it is generally possible to check the state of a component or event (such as Battery level, Notification content, WiFi connection...) testing appropriate Magic Text value. | For a trigger to fire, the macro must be available (i.e. ready to run, not disabled) at the exact time the event occurs. Otherwise, it is generally possible to check the state of a component or event (such as Battery level, Notification content, WiFi connection...) testing appropriate Magic Text value. | ||
| − | It is possible to add multiple triggers to a single macro and in this case any single trigger firing will cause the macro to be invoked | + | It is possible to add multiple triggers to a single macro and in this case any single trigger firing will cause the macro to be invoked. |
| − | As an alternative to combining triggers with an AND statement it is generally possible to add constraint logic to individual triggers such that they can be limited to | + | It is not possible to combine triggers with AND logic when using [[Constraint: Trigger Fired|Trigger Fired]] constraint (Basically saying "If trigger 1 fired AND trigger 2 fired") because a trigger is an instantaneous event, so it is not possible (or highly improbable) to get a state where two instantaneous events happen at exactly the same time. There's always exactly 1 trigger that started an execution of your macro actions. |
| + | |||
| + | As an alternative to combining triggers with an AND statement it is generally possible to add constraint logic to individual triggers such that they can be limited to fire when only some other state is also true. | ||
= List of Triggers = | = List of Triggers = | ||
Revision as of 09:51, 16 November 2023
A trigger is an instantaneous event that your device can detect to make a macro run. A macro must have at least one trigger to be valid.
For a trigger to fire, the macro must be available (i.e. ready to run, not disabled) at the exact time the event occurs. Otherwise, it is generally possible to check the state of a component or event (such as Battery level, Notification content, WiFi connection...) testing appropriate Magic Text value.
It is possible to add multiple triggers to a single macro and in this case any single trigger firing will cause the macro to be invoked.
It is not possible to combine triggers with AND logic when using Trigger Fired constraint (Basically saying "If trigger 1 fired AND trigger 2 fired") because a trigger is an instantaneous event, so it is not possible (or highly improbable) to get a state where two instantaneous events happen at exactly the same time. There's always exactly 1 trigger that started an execution of your macro actions.
As an alternative to combining triggers with an AND statement it is generally possible to add constraint logic to individual triggers such that they can be limited to fire when only some other state is also true.