Describe the bug
I've been using AltTab for a few days now and really enjoying it. Thanks again for the excellent app!
Here's a case of a small issue I'm having. It's probably a narrow case for a narrow set of users, so I wouldn't imagine it's worth prioritizing, but posting here if it's helpful to know about. And it might well be an issue with NoMachine, which seems to interact with MacOS in idiosyncratic ways.
Screenshots / video
(I'm not sure these would be helpful in this case but let me know anything else you need)
Steps to reproduce the bug
com.nomachine.nxdock to the "Blacklist"Hi @max-sixty! Thank you for sharing this issue!
Indeed, this is a regression introduced in v5 when I rewrote the whole keyboard input system, to avoid the Secure Input issue in macOS.
I have found a way to have this work as you expect. This will be delivered in the next-next release (next release is a hotfix for a crash at launch) 馃憤
Closing this issue as it should be fixed now. Please let me know if it persists somehow 馃憤
Thanks @lwouis !
Just to confirm, this is working really well!
Most helpful comment
Hi @max-sixty! Thank you for sharing this issue!
Indeed, this is a regression introduced in v5 when I rewrote the whole keyboard input system, to avoid the Secure Input issue in macOS.
I have found a way to have this work as you expect. This will be delivered in the next-next release (next release is a hotfix for a crash at launch) 馃憤