Constraint/Condition Request: Keyboard Active

[Masterobert]

Feature Request:
Add a `Keyboard Active` constraint/condition, where the macro/action is not invoked if the keyboard is active or not active.

More details:
When selecting the `Keyboard Active` option, give the user a prompt to select whether they wish the constraint/condition to be 'Keyboard Active` or `Keyboard Not Active`

Use case:
Certain macro actions interfere with the keyboard when an action is triggered.
For example, if the keyboard is active and a macro triggers the `Popup Message` action, the keyboard gets closed, interfering with the keyboard that the user was using.
A 'Keyboard Active' constraint/condition would prevent the macro/action from interfering with the keyboard.

As a user that deals with this on an almost daily basis, I would love for this to get added. Thanks!

 

[Jacob L]

Something like this may help but not in all cases: https://www.macrodroidlink.com/macrostore?id=7529

 

[Endercraft]

For constraint, you could use app foreground with the keyboard app. Works for me

 

[Masterobert]

For constraint, you could use app foreground with the keyboard app. Works for me

That's ingenious!

It totally slipped my mind that the keyboard is a (in my case, non-launchable) app! Thanks for pointing this out!

Although I'm sure this feature request would still benefit non-tech savvy people.

 

[Pepy]

For constraint, you could use app foreground with the keyboard app. Works for me

I can't get this to work on v5.43.8 with Gboard or Samsung keyboard