The release has full support for 2.20 Unicode KBFs (Customized layouts / KeyBoard File) created with IMG's Build-A-Board, but there are a few limitations partially due to the limits of the Android platform and partially due to design choices during the development of the software.
Fonts - custom fonts specified in Build-A-Board are not carried through, and the default/system font is used for all text display. Additionally various logic is used to address key and board scaling and to ensure that all text fits into the available space.
Key Images - Key Image data selected and used in Build-A-Board is not used - the Key Image selections in the My-T-Soft Keyboard Settings | Key Images are used as overrides, and there is no way to select/use the Boards Key Image. Note that the HiRes Key Type and Key Image Frame is required to enable use of these Key Images on the device. For the Regular Key Type, the frame options and text/face/highlight/shadow colors are fully supported.
When the Revert to Default Layout on Long Key Press is On, this effectively disables the repeatable key type for backspace or delete, as holding down the key triggers the Long Key press event.
Keys - Caps aware/shift states are handled internally based on single letter Key Labels/Key Actions. Various keys (e.g. arrows) use text handling logic vs. generating actual keystrokes to be interpreted by the text control. Due to the nature of how keys are translated and interpreted, the interface should clearly be understood as a virtual keyboard vs. a keyboard/keystroke emulator. If there are specific key issues, please contact IMG Technical Support.
Keyboard Moving - this option will act differently on different devices, so it may not be the best choice for all situations. You will not be able to move a board off the top or sides, and this will limit the usefulness on smaller screens.
Undocked / Top of screen layouts prevent actual touch/clicks directly below the displayed keyboard layout window.
The 2.20.16 update supports base key events using the [CMD:KEYCODE=???] where ??? is a decimal number specifying an Android internal keycode (e.g. KEYCODE_1 is decimal 8). This also provides support for the %%knnn syntax for these Android virtual codes.
My-T-Soft for Android 2.20.9 (first public release, September 2017)
My-T-Soft for Android 2.20.10 (October 2017) - includes support for Zebra Technologies DataWedge utility (Bar code scanning)
My-T-Soft for Android 2.20.11 (November 2017) - adds logic for managing DataWedge profiles from within My-T-Soft
My-T-Soft for Android 2.20.12 (March 2017) - adds Editor Input interpretation for tab and enter characters fed from DataWedge scanned data
My-T-Soft for Android 2.20.14 (June 2018) - adds CMD:KEYCODE support for raw key events. (Also begins version tagging that odd versions are development, even versions are public releases)
My-T-Soft for Android 2.20.16 (June 2018) - Updates [F1] - [F12] interpretaton to be key events (F1 = Keycode 131, etc.) Also resolved key event constructor issue.
My-T-Soft for Android 2.20.18 (July 2018) - Includes Force Visibility option and has Import/Export options for settings. Also support for Android 8 (Oreo)
|Category: General||Type: Information||Product: My-T-Soft for Android||Version: 2.20|