Search results

I haven't seen this before because I only started trying it out recently! As stated I do not get the problem if I force close the app - hence force closing also has a very different behaviour from my visibility!

So I guess we both have the problem ... Hopefully the owner can help!!

Ok ... If I just have the floating text it shows ok and can be discarded ok. If I display the floating text before the bubble ... The bubble is displayed first and the floating text only shows after the bubble is cleared. If I add a wait between the two it gets messy!! If I am inside MacroDroid...

Ok do you want another screen recording of it!! Not sure what you mean by authorization! If MacroDroid is closed it does not kick it open!

This is my screen recording. I start it using Panels but it does the same when running via MacroDroid test. The bubble pops up. I drag it away and then MacroDroid comes up (unless I force killed it beforehand) Screen Recording

I found that if I close MacroDroid (force close) then hiding the bubble does what you expect. But if MacroDroid is running in the background then it comes to the foreground!!

It just consists of this single action

I just tried using the bubble action. When I close the bubble it automatically reopens MacroDroid no matter the previous activity I was doing Is that a way to prevent this? Version 5.44 Google Pixel 8 Pro Android 14

Yep works for me too. Thanks 👍

Sure no problem Google Pixel 8 Pro Android 14 UQ1A.231205.015 Google Pixel Launcher I presume that apps like Tasker and Automate must spot something in the request to create the shortcut that causes it to behave differently!! But how do we create a bug report for this?? So that the dev can...

I have the same problem. How can this be raised as a bug! I can create shortcuts for other apps like Automate using Panels but not Macrodroid. I have switched from using the Macrodroid Drawer to use Panels and this is a major issue as it is not possible to launch a Macro externally from what I...

As an added reason for wanting this. Below is the test output from a simple script listening on two intents 1 and 2 called from Tasker which also passes a variable stored by the trigger in the same variable. As you can see the local variable is overwritten by the 2nd call so variables do not...

It's not that the trigger doesn't fire. It fires but if the task is still running when the 2nd trigger fires I want the first task to end immediately and allow the new task that has been triggered by a different trigger to run instead.

That's why this is in Feature Request!! 😃 The problem is knowing at what point the 2nd trigger will happen. Hence the need to cancel from the new task.

Understood. - that's the point - it would be helpful (in some circumstances) to be able to only run the latest instance from the latest trigger - or to be able to cancel the previous instances (if still running) and continue with the latest trigger only.

It would be helpful in some instances to single thread a macro. Either enable a macro to auto cancel other instances of itself or allow the Cancel Macro to cancel other instances of itself but not itself. I have a couple of triggers on a macro that in some instances can trigger quickly - eg...