Action block constraints

Quidn

Passionate Member
To be clarified, do you want something different to this? If so, please explain in more detail to figure out what you want.

Screenshot_20230926_141932_MacroDroid.png
 

HawkerPaul

New member
I'm talking about action blocks here, not macros or actions within macros.
I would like to see a constraint section (the section with a green background) at the end of an action block as per regular macros.
 

Dm114

Well-known member
I'm talking about action blocks here, not macros or actions within macros.
I would like to see a constraint section (the section with a green background) at the end of an action block as per regular macros.
Global constraints (with the green background) are made to prevent a macro from running in some circumstances despite trigger firing.

For Action blocks calls, the calling macros call these Action blocks programmatically, depending on some conditions. These conditions can be tested either with an If... statement or with a constraint added to the Action block call.
 

HawkerPaul

New member
Thanks for the replies.
I am aware of this, but it can be useful to put constraints on the action block itself, as instead of multiple calls to an action block within macros, testing each call with individual constraints or if conditions, it would be far easier to attach these conditions onto the action block itself.
For example, you might run an action block only when a certain condition arises or variable has been set.
 

Dm114

Well-known member
Thanks for the replies.
I am aware of this, but it can be useful to put constraints on the action block itself, as instead of multiple calls to an action block within macros, testing each call with individual constraints or if conditions, it would be far easier to attach these conditions onto the action block itself.
For example, you might run an action block only when a certain condition arises or variable has been set.
Indeed... Why not?

If it's to hard to implement for @MacroDroidDev, as a workaround you can either begin your action block with a:
1⁰ IF (conditions) THEN (action block's actions) ENDIF
2⁰ EXIT ACTION BLOCK with appropriate constraints
 

Quidn

Passionate Member
The former one was an example to be compared to the Constraints in a macro, but aren't they just near identical? That's why I asked to you some more details.

Screenshot_20230926_152023_MacroDroid.png
 

HawkerPaul

New member
Yes @Quidn. This has the same effext, along with putting if statements at the start of the macro.
However it would be easier to have a constraint section which is inkeeping with how we all write macros, making it more logical and intuitive in my opinion
 

Quidn

Passionate Member
All right, I fully agree that having constraints section in Action Blocks would be more intuitive to users already been familiar to MacroDroid interface.

I never want to eliminate any of claimed feature requests, but in my experience it might been pushed down in priority if there's a simple workaround, even though it's relatively simpler to be implemented than other newly added features.

As far as I know every features missing in Action Blocks are missed by some technical reasons. And Exit Action Block is a specialized action for Action Blocks. I'm guessing the missing of constraints might be one of the reasons to Exit Action Block was created only in the Action Blocks.

But who knows, there may be added constraints section there in the next release. 😀
 

CDA

Member
I would also like a constraint section for action blocks.

I use Action blocks instead of actions on several macros (so instead of editing each macro to change something like a notification sound, I just edit the action block). Would be really nice to be able to set a constraint on either the whole action block or actions within it, would really streamline a lot of my macros and editing them.
 
Top