Describe the bug
I set up 3 finger swipe down for keyboard shortcut "Crtl + W" (or ^ W). When I trigger it in Microsoft Remote Desktop 10 client, it triggers successfully (I have feedback setup as well), but only the key "W" goes through. So each 3 finger swipe down results in typing a "W" instead of closing the current tab (via Ctrl W).
Additional information (e.g. StackTraces, related issues, screenshots, workarounds, etc.):
I looked up this issue and found this Github issue which indicates it should be fixed by v2.353. I'm running v3.086 and have enabled "Shortcut sending compatibility mode", but am still not able to get it to work.
Note: Before bug reporting, please make sure you have the latest version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app from the "User Diagnostic Reports" section.
Still experiencing this same issue.
I used to love BTT when I had my old mac. I spend much of my day working in Amazon Workspaces doing development for work. Therefore, I bought a new BTT license with the goal of creating many automations that would help my workflow.
However, I am experiencing the same issue as described above, namely that modifier keys are not passed through to the remote machine.
e.g.
two finger tip-tap-right mapped to Ctrl-C only passes in "C". This is the same issue with all modifier keys.
It seems that the same bug has been opened for many different remote desktop applications and use cases. See below:
I am using BTT Version 3.504 on a MacBook Pro 16 inch on macOS Big Sur 11.1 and connect to a Linux Amazon Workspace. My modifier keys work in my linux workspace when pressed on the keyboard.
Squashing this bug or providing a workaround would be really appreciated.
But some seem to ignore pretty much all programatically generated modifier events (Karabiner Elements works because it works at a much lower level than BTT)
Thanks for the quick response and explanation. Unfortunately, neither of those two workarounds solved the problem for me. Out of curiosity, why is it able to send the non-modifier keys if it's unable to handle programmatically created events?
Is there something else going on in addition to this perhaps? It seems that windows machines can pass modifier keys to remote windows machines which makes it sound like not an app issue?
Yes, I think they handle programatically generated modifier keys differently for different operating systems, but unfortunately I have no idea what is the logic behind it ;-(
I think I might have found some obscure way to send the events in a way that is handled correctly by at least the Microsoft Remote Desktop :-). I'll need to do more testing though as it's currently pretty fragile.
I also have this issue with the Microsoft Remote Desktop app.
But I got myself a workaround. I installed Parallels Desktop, created a Windows 11 VM, and have the remote connection from there. BTT triggers work well even when RDP is in Coherence mode.
Update: Another alternative is to use Parallels Client as RDP client. Make sure you enable the "Shortcut Sending Compatibility Mode"
