Search results

Motivation: I have a macro that replaces my regular mail notification and has over 30 chained else-if conditions for modifications to the notification in various cases. The more I add, the longer it's taking to find anything, because all the else-if conditions are not in any logical order, but...

I have a system of macro that uses mostly just screen on/off state (and for how long), also two quick action tiles to indicate state and to manually override it and some extra conditions like calendar events, which I use for my own sleep/awake detection and alarm setting. Should I share it? It...

You can definitely export macros as XML and that contains the actual variable names, maybe they're stored like that internally, too.

There was a similar thread about this here before and it basically came down to the effort of implementing. MacroDroid would have to find and update every stopwatch start/stop/reset action, every stopwatch constraint, every stopwatch trigger (and maybe even re-schedule alarms), every stopwatch...

I know, but for example right now I'm making a macro called "screen_off" that gets triggered by "Screen off", has the action "Stopwatch start: screen_off" and the constraint "alarm_set=false", nothing more. Despite seeming so simple, it actually took me hours of planning and multiple revisions...

I don't know why this limit even exists, or rather why it's so low, but I keep getting issues with it. Some of my macros are quite complicated, so they would benefit a lot from longer descriptions. Currently MacroDroid actively discourages good documentation.

The only time that stopwatches can currently be set to is 0. I would like to be able to set them to any value, it would be especially helpful if the time could be determined by an integer variable (as number of seconds). Usecase: I have a pretty complicated set of macros that tries to determine...