Difference between revisions of "Triggers"
| (13 intermediate revisions by 4 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. |
| − | 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 = | ||
| Line 84: | 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 94: | Line 100: | ||
[[Trigger: Logcat Message|Logcat Message]] | [[Trigger: Logcat Message|Logcat Message]] | ||
| + | |||
| + | [[Trigger: Macro enabled|Macro enabled]] | ||
| + | |||
| + | [[Trigger: Macro finished|Macro finished]] | ||
[[Trigger: MacroDroid Drawer Open/Close|MacroDroid Drawer Open/Close]] | [[Trigger: MacroDroid Drawer Open/Close|MacroDroid Drawer Open/Close]] | ||
| Line 116: | Line 126: | ||
[[Trigger: Notification Bar Button|Notification Bar Button]] | [[Trigger: Notification Bar Button|Notification Bar Button]] | ||
| + | |||
| + | [[Trigger: Power Button Long Press|Power Button Long Press]] | ||
[[Trigger: Power Button Toggle|Power Button Toggle]] | [[Trigger: Power Button Toggle|Power Button Toggle]] | ||
| Line 154: | Line 166: | ||
[[Trigger: SMS Sent|SMS Sent]] | [[Trigger: SMS Sent|SMS Sent]] | ||
| + | |||
| + | [[Trigger: Spotify|Spotify]] | ||
[[Trigger: Stopwatch|Stopwatch]] | [[Trigger: Stopwatch|Stopwatch]] | ||
| Line 162: | Line 176: | ||
[[Trigger: System log|System Log Entry]] | [[Trigger: System log|System Log Entry]] | ||
| + | |||
| + | [[Trigger: System Setting Change|System Setting Change]] | ||
[[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: USB Device Connect/Disconnect|USB Device Connect/Disconnect]] | [[Trigger: USB Device Connect/Disconnect|USB Device Connect/Disconnect]] | ||
Latest 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.