Difference between revisions of "Constraints"

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:

@@ Line 1: / Line 1: @@
-Constraints are optional and can be used to allow or prevent a macro/action from running based on certain conditions.
+<span style="color: #0E9549; font-size: 24px;">'''What is a constraint?'''</span>
-Constraints can be placed on macros to allow or prevent the entire macro firing based on the set condition(s). You can also add constraints directly to individual triggers and actions from the 'Edit Macro' screen, by clicking on the trigger/action and selecting "Add constraint"
+Constraints in MacroDroid are optional tools that allow you to control when a macro or a specific action is triggered.
-A constraint is evaluated at the point a trigger fires or actions runs and a macro/action will only run if the <strong>constraint condition is true.</strong>
+They are based on certain conditions that must be met to allow or prevent the execution of macros and actions.
-By default if adding more than one constraint to a macro they will be combined with an AND condition (e.g. all added constraints must be true). This can be changed in the dropdown in the constraints title to an OR condition. In this case only one of the added constraints needs to be true for the macro to run.
-<strong>Nesting constraints</strong>
+<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:
-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
@@ Line 17: / Line 33: @@
        | - 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 ==
+<span style="color: #0E9549; font-size: 24px;"><strong>List of Constraints</strong></span>
+[[Constraint: ADB Hacked|ADB Hacked]]
 [[Constraint: Airplane Mode|Airplane Mode]]
-[[Constraint: AND / OR / NOT|AND / OR / NOT]]
+[[Constraint: AND / OR / XOR / NOT|AND / OR / XOR / NOT]]
 [[Constraint: Application Running|Application Running]]
@@ Line 43: / Line 62: @@
 [[Constraint: Call State|Call State]]
+[[Constraint: Category Enabled/Disabled|Category Enabled/Disabled]]
 [[Constraint: Cell Towers|Cell Towers]]
+[[Constraint: Clipboard content|Clipboard content]]
+[[Constraint: Compare Values|Compare Values]]
 [[Constraint: Dark Mode|Dark Mode]]
@@ Line 57: / Line 82: @@
 [[Constraint: Device Orientation|Device Orientation]]
+[[Constraint: Floating Button|Floating Button]]
+[[Constraint: Floating Text|Floating Text]]
+[[Constraint: Geofence|Geofence (Location)]]
 [[Constraint: GPS State|GPS State]]
 [[Constraint: Headphone Connection|Headphone Connection]]
+[[Constraint: IP address|IP address]]
 [[Constraint: Is Roaming|Is Roaming]]
@@ Line 67: / Line 100: @@
 [[Constraint: Location Mode|Location Mode]]
+[[Constraint: Macro Running|Macro Running]]
 [[Constraint: Macro(s) Enabled/Disabled|Macro(s) Enabled/Disabled]]
 [[Constraint: Macro(s) Invoked/Not invoked Recently|Macro(s) Invoked/Not invoked Recently]]
+[[Constraint: MacroDroid Invocation Method|MacroDroid Invocation Method]]
 [[Constraint: MacroDroid Mode|MacroDroid Mode]]
@@ Line 97: / Line 134: @@
 [[Constraint: Proximity Sensor|Proximity Sensor]]
+[[Constraint: Quick Tile State|Quick Tile State]]
 [[Constraint: Ringer Volume|Ringer Volume]]
@@ Line 111: / Line 150: @@
 [[Constraint: Sunrise/Sunset|Sunrise/Sunset]]
+[[Constraint: System Settings|System Settings]]
 [[Constraint: Time of Day|Time of Day]]