Difference between revisions of "Triggers"
m (added Power Button Long Press) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <pre class="header-style> | ||
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. | 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 | + | For a trigger to fire, the macro must be enabled (i.e. ready to run, not disabled) at the exact time the event occurs. |
| + | </pre> | ||
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. | ||
| Line 86: | Line 88: | ||
[[Trigger: Hotspot Enabled/Disabled|Hotspot Enabled/Disabled]] | [[Trigger: Hotspot Enabled/Disabled|Hotspot Enabled/Disabled]] | ||
| + | |||
| + | [[Trigger: HTTP Server Request|HTTP Server Request]] | ||
[[Trigger: Intent Received|Intent Received]] | [[Trigger: Intent Received|Intent Received]] | ||
| Line 176: | Line 180: | ||
[[Trigger: Tasker/Locale Plugin|Tasker/Locale Plugin]] | [[Trigger: Tasker/Locale Plugin|Tasker/Locale Plugin]] | ||
| + | |||
| + | [[Trigger: Text Shared to MacroDroid|Text Shared to MacroDroid]] | ||
[[Trigger: UI Click|UI Click]] | [[Trigger: UI Click|UI Click]] | ||
Revision as of 22:17, 10 June 2024
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 enabled (i.e. ready to run, not disabled) at the exact time the event occurs.
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.