It seems that BMTP is missing the release of the command key after switching apps that are running in different desktop/spaces after using the shortcut command+tab.
You can use this small project to check this issue:
CMD PRESSED-RELEASED.bmtp (1.7 KB)
The project perform three actions:
- after pressing the command key, it shows the log ‘CMD PRESSED’
- after releasing the command key, it shows the log ‘CMD RELEASED’ and the notification ‘CMD RELEASED’
- after pressing the shortcut command+F12, it shows the log ‘CMD+F12 PRESSED’ and the notification ‘CMD+F12 PRESSED’
Steps to reproduce the issue:
- Open any app in desktop 1 (i.e. System Settings)
- Open any other app in desktop 2 (i.e. TextEdit)
- Go to desktop 2 and activate TextEdit
- Use the command+tab shortcut to select the System Settings app
- Release the command key
- The System Settings app is activated and desktop 2 changes to desktop 1
- Now press F12 key alone. Everytime you press the F12 key alone, you will see the notification ‘CMD+F12 PRESSED’. It seems that BMTP is not aware that the command key has been released, and it reacts as the command key is still pressed.
- Pressing and releasing the command key stops the issue
The issue occurs with any app change. System Settings and TextEdit are just examples.
Using BMTP 1.9.1 build 1064 and macOS Sonoma 14.7.1
I would appreciate if you could fix this issue as soon as possible. Thanks a lot.