Disable/enable specified triggers using actions (already been implemented)

LF0

Member
Due to certain reasons, I need to consider disabling specific triggers in certain situations. Please consider adding an action to MacroDroid that allows for disabling/enabling specified triggers within itself or other macros. This way, I won't have to disable the entire macro.
 

hsurB

Well-known member
For now you can use variables, change them when you want to disable trigger and add variable as constraint to that trigger.
 

LF0

Member
For now you can use variables, change them when you want to disable trigger and add variable as constraint to that trigger.
I know how to use variables and constraints, but what I need is the ability to disable a specific trigger. Let me give you an example. If I use the Screen Content trigger, even if I apply constraints to it, it will keep repeatedly reading the screen when it's not triggered. To address this, I created another macro to disable all macros that use the Screen Content trigger when I don't need them. However, this also means I have to separate the functionalities that need to be preserved into multiple macros to prevent them from being disabled. It becomes inconvenient and requires a lot of variables for communication.
 

Dm114

Well-known member
I think this can be added for v5.39,you should send an email to support@macrodroid.com and explain your request (honestly it works way better than here).
I'm not sure it's a good idea to send feature requests to this mail address which is dedicated to troubleshooting.

As you know, Jamie is heavily overworked with solving issues due to new MD versions, on one hand, answering as fast and as completely as possible to requests here on the forum, on the other hand. On a third hand (!) he also tries to improve MD more and more and fights to comply to G**gle requirements. According to his fouth hand, it is probably dedicated to his regular job! 😉😃
 

hsurB

Well-known member
Not gonna lie, priority list of incoming features somewhere could be decent idea.
List somewhere few the most often asked features to add and vote what we would like to get first or something.
After adding so many new things lately (javascript action etc.), I don't think Jamie is that busy at all 😅😂
 

Dm114

Well-known member
Not gonna lie, priority list of incoming features somewhere could be decent idea.
List somewhere few the most often asked features to add and vote what we would like to get first or something.
After adding so many new things lately (javascript action etc.), I don't think Jamie is that busy at all 😅😂
To make his opinion among all feature requests, Jamie has at least 3 criteria: the number of positive reactions, his own opinion about the opportunity of adding such feature (to avoid too specific requests) and the amount of job (hours) needed to achieve a smooth integration to MD...
 

MacroDroidDev

Administrator
Staff member
Just to be clear, I do look here but not as often as I should. I have been very busy lately with lots of things, but I will try and cherry pick a few of the best ideas from the feature request.

The amount of work required is certainly a major consideration. The trouble is it's not always obvious how much work any give thing will be, sometimes I think something will be easy and it turns out to be a total nightmare. Many times I start adding some new feature and it turns out to be impossible or just so much work I have to abandon it, which is deeply frustrating but I don't want to get bogged down with the sunk cost fallacy.
 
Top