Difference between revisions of "Constraints"
(Missing additions to 5.40) |
m |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <span style="color: #0E9549; font-size: 24px;">'''What is a constraint?'''</span> | |
| − | Constraints | + | Constraints in MacroDroid are optional tools that allow you to control when a macro or a specific action is triggered. |
| − | + | They are based on certain conditions that must be met to allow or prevent the execution of macros and actions. | |
| − | |||
| − | < | + | <span style="color: #0E9549; font-size: 24px;">'''Apply to entire macros:'''</span> |
| + | |||
| + | You can apply constraints to an entire macro (at the bottom of the 'Constraints' tab). | ||
| + | |||
| + | This means that the macro will only be activated if the conditions set by the constraints are met. | ||
| + | |||
| + | <span style="color: #0E9549; font-size: 24px;">'''Restrictions on Triggers and Individual Actions:'''</span> | ||
| + | |||
| + | As well as being applied to an entire macro, constraints can be added directly to individual triggers and actions. | ||
| + | |||
| + | This is done from the 'Edit Macro' screen by selecting the trigger or action and selecting 'Add Constraint'. | ||
| + | |||
| + | <span style="color: #0E9549; font-size: 24px;">'''Nesting constraints'''</span> | ||
| + | |||
| + | If you need more sophisticated logic applied to constraint there is a special AND/OR/XOR/NOT constraint that can be used. | ||
| + | |||
| + | Any constraints nested under the logic constraint will have that logic operator applied. It's also possible to nest multiple logic constraints to create complex logic. | ||
| + | For example: | ||
| + | |||
| − | |||
AND | AND | ||
| Line 19: | Line 35: | ||
In the above example, Constraint 1 must always be true '''AND''' at least one of (Constraint 2 '''OR''' Constraint 3) must be true. | In the above example, Constraint 1 must always be true '''AND''' at least one of (Constraint 2 '''OR''' Constraint 3) must be true. | ||
| − | = | + | <span style="color: #0E9549; font-size: 24px;"><strong>List of Constraints</strong></span> |
[[Constraint: ADB Hacked|ADB Hacked]] | [[Constraint: ADB Hacked|ADB Hacked]] | ||
| Line 52: | Line 68: | ||
[[Constraint: Clipboard content|Clipboard content]] | [[Constraint: Clipboard content|Clipboard content]] | ||
| + | |||
| + | [[Constraint: Compare Values|Compare Values]] | ||
[[Constraint: Dark Mode|Dark Mode]] | [[Constraint: Dark Mode|Dark Mode]] | ||
| Line 65: | Line 83: | ||
[[Constraint: Device Orientation|Device Orientation]] | [[Constraint: Device Orientation|Device Orientation]] | ||
| − | [[Constraint: Floating | + | [[Constraint: Floating Button|Floating Button]] |
[[Constraint: Floating Text|Floating Text]] | [[Constraint: Floating Text|Floating Text]] | ||
| Line 82: | Line 100: | ||
[[Constraint: Location Mode|Location Mode]] | [[Constraint: Location Mode|Location Mode]] | ||
| + | |||
| + | [[Constraint: Macro Running|Macro Running]] | ||
[[Constraint: Macro(s) Enabled/Disabled|Macro(s) Enabled/Disabled]] | [[Constraint: Macro(s) Enabled/Disabled|Macro(s) Enabled/Disabled]] | ||
| Line 115: | Line 135: | ||
[[Constraint: Proximity Sensor|Proximity Sensor]] | [[Constraint: Proximity Sensor|Proximity Sensor]] | ||
| − | [[Constraint: Quick | + | [[Constraint: Quick Tile State|Quick Tile State]] |
[[Constraint: Ringer Volume|Ringer Volume]] | [[Constraint: Ringer Volume|Ringer Volume]] | ||
| Line 130: | Line 150: | ||
[[Constraint: Sunrise/Sunset|Sunrise/Sunset]] | [[Constraint: Sunrise/Sunset|Sunrise/Sunset]] | ||
| + | |||
| + | [[Constraint: System Settings|System Settings]] | ||
[[Constraint: Time of Day|Time of Day]] | [[Constraint: Time of Day|Time of Day]] | ||
Latest revision as of 15:51, 23 April 2024
What is a constraint?
Constraints in MacroDroid are optional tools that allow you to control when a macro or a specific action is triggered.
They are based on certain conditions that must be met to allow or prevent the execution of macros and actions.
Apply to entire macros:
You can apply constraints to an entire macro (at the bottom of the 'Constraints' tab).
This means that the macro will only be activated if the conditions set by the constraints are met.
Restrictions on Triggers and Individual Actions:
As well as being applied to an entire macro, constraints can be added directly to individual triggers and actions.
This is done from the 'Edit Macro' screen by selecting the trigger or action and selecting 'Add Constraint'.
Nesting constraints
If you need more sophisticated logic applied to constraint there is a special AND/OR/XOR/NOT constraint that can be used.
Any constraints nested under the logic constraint will have that logic operator applied. It's also possible to nest multiple logic constraints to create complex logic. For example:
AND
| - Constraint 1
| - OR
| - Constraint 2
| - Constraint 3
In the above example, Constraint 1 must always be true AND at least one of (Constraint 2 OR Constraint 3) must be true.
List of Constraints
Macro(s) Invoked/Not invoked Recently