Describe the bug
I use a keyboard shortcut (F13) to "Type text" with "Insert text by typing". None of the text will ever remain capitalized. For example, if it is set to "Hello", it will type "hello" instead. If I use the "Insert text by pasting" method, it does work. However, the application I'm using needs to use the typing method.
Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):
Any keyboard to invoke this action--probably doesn't work when invoked via a mouse, etc.
Screenshots
n/a
Device information:
Type of Mac: iMac 5k
macOS version: 10.14.3
BetterTouchTool version: 2.428
Additional information (e.g. StackTraces, related issues, screenshots, workarounds, etc.):
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.
You are correct, I am using Jump Desktop which allows me to remote into a Windows 10 machine. It will only type lower-case letters. Is there any workaround (other than pasting, which DOES show upper case letters, but which doesn't invoke the same response as the typing action).
Compatibility mode didn't help--it left lower-case letters and the events were sent out of order. For now, I have it broken down into many different actions where it sends specific upper-case key strokes individually and then "types out" the lower-case letters so that I don't have to have one action per letter. If you come up with a fix, please let me know. Thank you for your hard work!
I'm having the same issue with the native macOS Screen Sharing app. It has a known issue where when remote is Linux, cut-and-paste works remote-to-local, but not local-to-remote. I thought I had found a solution with the "Type contents" paste, but it always types lower case (the shift goes missing).
Same issue with BTT 3.402 and an xterm in XQuartz 2.7.11. Trying moeharri's suggestion with sending Shift Up and Shift Down only got the system confused about the state of the shift key, believing it was down no matter if Shift Up or Shift Down was the last item, no matter which application I used the typing shortcut in. Restarting BTT was the way to set things right. (Does "Down" and "Up" refer to pressing and releasing the physical key or what it's supposed to do to the characters following it?)