Recent content by Pseudocyclic

Or this (not as precise, but might be sufficient in practice): T1 = button1 T2 = button2 A = if trigger fired = T1 A = wait until trigger fired = button2 (cancel after 1s timeout) A = else A = wait until trigger fired = button1 (cancel after 1s timeout) A = end if A = pause media player

Try this: T1 = button1 T2 = button2 A = if trigger fired = T1 A = set Iinteger to Iinteger +1 A = else A = set Iinteger to Iinteger -1 A = end if A = wait 100ms A = if Iinteger = 0 A = pause media player A = else A = set Iinteger to 0 A = end if A = cancel macro actions

Probably not much in it but I think Macro Not Running [This Macro] is easier/quicker to set up. I used to use Rooted Device - Rooted (because my device isn't) but maybe one day...

What happens if you test the second macro first and then the first macro second?

When I use If - End Ifs with multiple Else Ifs I often want to maintain a certain order (eg alphabetic) for the Else Ifs to simplify updating and maintenance. For this reason I never use the initial If because it can't be re-positioned like the Else Ifs can. So for the initial If I always use a...

So I guess the best workaround might be to install MacroDroid on every device and use it to zap the unwanted notifications...?

Will this ALWAYS return false?

How to prevent unwanted notifications being duplicated on devices other than the intended one?

Thanks for that, I've got it now. I tested again, then switched the positions of the triggers, and then re-tested. Whichever trigger is in the first position is the one that fires. Thanks again!

Merged macro DOES have TWO triggers - one trigger from each of the two macros that I merged, ie 'Bluetooth event - device connected - any' AND 'Bluetooth event - device connected - headset'.

Thanks. Mobile view is the fix. PS - works a treat with Block Screen Touches action!

I just merged two macros. One had the trigger 'Bluetooth event - device connected - any' and the other had the trigger 'Bluetooth event - device connected - headset'. When headset connected, both of the 'old' macros were triggered. I presumed that now, when headset connected, the 'new' macro...

When using the script editor I am not seeing any 'save' option - am I missing something obvious?

Please post a screenshot (preferably in English) of your macro.