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.For now you can use variables, change them when you want to disable trigger and add variable as constraint to that trigger.
I'm not sure it's a good idea to send feature requests to this mail address which is dedicated to troubleshooting.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).
Holding Control and Alt keys allows typing in multiple places in visual studio. I wonder if that's the case with Android studioAh yes, having 4 hands to code faster, what a good idea!
Ok for 4 hands but he'll need 2 brains!Ah yes, having 4 hands to code faster, what a good idea!
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...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