Keyboard shortcuts are case sensitive and ones with symbols are not recognized
Thanks to user reports we have just been made aware of these issues:
PadKeys is case-sensitive: If you have a shortcut "xx" -> "something", then typing "Xx" will not trigger the shortcut. You have to type "xx".
PadKeys won't recognize shortcuts like "x@y" -> "xray1@yowzer.com" at all.
We are working on these and hope to submit a new version to the App Store in a couple of days. As always, folks interested in getting the fix sooner can open a ticket with us and we'll add you to the list to receive beta versions through TestFlight before they are released in the Store.
Thanks for your patience!
OK this has been taken care of in 1.3.2. Sorry it took so long to get out, there was an unrelated issue that derailed the review process a bit.
Please open a new issue if something is still not behaving as expected.
-
AdminTypefinity (Support, Typefinity) commented
Yes, this will behave differently in the immediately upcoming version. You will be able to type 'xyz' to access the shortcut in either case. The casing will still be imposed if you DO type Xyz. I believe the system keyboard does this also, but if it doesn't, and the capitalization is annoying, we will address that too in a subsequent version.
-
dale commented
Additional info on this issue.
I have a shortcut as xzy -> Xxxx ttt nnn, ZZZ, Yyy yyyy.
If I leave the shortcut as lower case in the settings and type it with PadKeys as lower case it expands properly.However, if I change the shortcut to:
Xyz it auto capitalizes my text. in the example above the ZZZ is supposed to be three uppercase letters, however it ends up being expanded as ZzzI have auto-capitalize in PadKeys turned off.