Difference between revisions of "Actions"
| Line 238: | Line 238: | ||
[[Action: Secure Settings|Secure Settings]] | [[Action: Secure Settings|Secure Settings]] | ||
| − | [[Action: Selecttion Dialog| | + | [[Action: Selecttion Dialog|Selection Dialog]] |
[[Action: Send Email|Send Email]] | [[Action: Send Email|Send Email]] | ||
| Line 272: | Line 272: | ||
[[Action: Share Last Photo|Share Last Photo]] | [[Action: Share Last Photo|Share Last Photo]] | ||
| − | [[Action: Share Text| | + | [[Action: Share Text|Share Text]] |
[[Action: Share Location|Share Location]] | [[Action: Share Location|Share Location]] | ||
Revision as of 17:07, 8 January 2024
An action is something your device can do when a macro runs. A macro must have at least one action to be valid.
Synchronous vs asynchronous
Most of MacroDroid actions take a minuscule amount of time to execute. But some actions such as HTTP request or a shell script action can take a significant time to complete. Some of these actions have an option to "Block next action until complete" in their configuration GUI. If this option is enabled subsequent actions will wait until this action completes before continuing. If the option is disabled the action will run asynchronously while other actions continue. In conventional programming languages you would probably be able to pass a callback to call when the execution is complete to perform some other actions after the asynchronous action has completed (possibly even work with the data if the asynchronous action returned some), but because MacroDroid inner workings are rather arbitrary there is usually no such systematic option and you need to rely on different workarounds.
Control flow
List of Actions
Notification LED Enable/Disable
Priority Mode / Do Not Disturb