I use the Unlock Screen action in a named trigger and sometime in recent (one of the past several) updates of BTT, it has started
- frequently failing to cleanly execute the passphrase keystrokes and so failing to unlock the screen
- sending additional keystrokes after successfully unlocking the screen which then have the effect of causing strange things to happen in existing windows on the screen.
Is there anyone else using this action who has seen similar?
Is this reproducible on someone else's box or is it just me?