I have a macro that uses UI Interactions (automated touches) to do a few things. Once I start it, while a specific app is in the foreground, it does the automated touches every 5 seconds. (what exactly it does is not important)
I start it using a quick tile but I can't stop it that way because it might actually touch some notifications or other quick tiles. So this is actually the first problem. The condition I have that says while the app is in the foreground but it doesn't recognize if the notification shade is pulled down over the top of the foreground app so it keeps trying to click even while the notifications shade is pulled down.
If you follow me so far, then my first suggestion for an enhancement request should be pretty obvious given my situation.
#1. Add a constraint that can detect if the notification shade is pulled down.
I'm hoping that's possible to implement easily and following down that same path, my guess is that it probably won't recognize when the notification shade is pulled down until it is completely pulled down or pulled down to some arbitrary point, but in my scenario what I really need is a way to tell if someone is in the process of pulling down the notification shade also. If that's a built-in constraint that can be easily added then that would be perfect.
#2. Add a constraint that can detect if the notification shade is in the process of being pulled down.
Assuming that's not possible, and really even if it is, another way to accomplish the same goal as #2 would be to try to determine if the screen is actively being touched. This might actually be a more general way to address the problem I'm having.
#3. Add a constraint that can determine if the screen is actively being touched, i.e. the user is actively in the process of pulling down the notification shade (or obviously for any other reason). This should have an option to filter out touches that are done programmatically by a macrodroid UI Interaction so that in my case it does not generate false positives in that way.
I start it using a quick tile but I can't stop it that way because it might actually touch some notifications or other quick tiles. So this is actually the first problem. The condition I have that says while the app is in the foreground but it doesn't recognize if the notification shade is pulled down over the top of the foreground app so it keeps trying to click even while the notifications shade is pulled down.
If you follow me so far, then my first suggestion for an enhancement request should be pretty obvious given my situation.
#1. Add a constraint that can detect if the notification shade is pulled down.
I'm hoping that's possible to implement easily and following down that same path, my guess is that it probably won't recognize when the notification shade is pulled down until it is completely pulled down or pulled down to some arbitrary point, but in my scenario what I really need is a way to tell if someone is in the process of pulling down the notification shade also. If that's a built-in constraint that can be easily added then that would be perfect.
#2. Add a constraint that can detect if the notification shade is in the process of being pulled down.
Assuming that's not possible, and really even if it is, another way to accomplish the same goal as #2 would be to try to determine if the screen is actively being touched. This might actually be a more general way to address the problem I'm having.
#3. Add a constraint that can determine if the screen is actively being touched, i.e. the user is actively in the process of pulling down the notification shade (or obviously for any other reason). This should have an option to filter out touches that are done programmatically by a macrodroid UI Interaction so that in my case it does not generate false positives in that way.