In order to provide backwards support for the 2.20.32 release that can run on Android 5.1 to 8.1 (API 22-27), and due to required code changes for updating to Android 9 (API 28), there are now 2 distinct Android releases. The original release and update notes continue after the notes on the current release.

This release is built targeting Android 9 (API 28), and no attempt was made to provide backwards compatibility. There were several key deprecated API calls that required updating the code, and with additional changes anticipated for Android 10, it made sense to take this targeted approach.

The main update revolves around adding an undocked, or floating keyboard option (under My-T-Soft Operation options). When enabled, the keyboard is displayed as a floating "popup" window, and with the appropriate move option (Keyboard Moving), it can be dragged as needed. It will still operate as any standard IME in terms of hiding and showing due to text input. Note that in Multi Window mode (where multiple windows are visible on the screen), the floating keyboard must be over the window you want to type into.

My-T-Soft for Android 2.20.102 (first Android 9 release, November 2020)

My-T-Soft for Android 2.20.32 Release Notes

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.32 (November 2018) - license issue when not in apk, support default layout from Build-A-Board.com account in addition to favorites.
My-T-Soft for Android 2.20.30 (September 2018) - addresses Long Press setting at device reboot.
My-T-Soft for Android 2.20.28 (September 2018) - correct Bar Code Scanner Interface setting for Zebra/Honeywell devices at startup / BOARDS folder logic to prevent KBF overwrites.
My-T-Soft for Android 2.20.26 (September 2018) -Scan Tab/Enter Key feature to handle as keystrokes or editor actions. Additional scanner.txt overrides (additonal 2 hardware key triggers, prefix/suffix options).
My-T-Soft for Android 2.20.24 (September 2018) - Additional support for Honeywell barcode scanners and scanner.txt overrides (hardware key triggers, trigger options, external scanner).
My-T-Soft for Android 2.20.22 (September 2018) - Additional support for Honeywell barcode scanners and auto-import options for account/preferences (My-T-Soft_Import folder).
My-T-Soft for Android 2.20.20 (August 2018) - Adds support for Honeywell barcode scanners and embedded license options.
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)
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.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.12 (March 2017) - adds Editor Input interpretation for tab and enter characters fed from DataWedge scanned data
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.10 (October 2017) - includes support for Zebra Technologies DataWedge utility (Bar code scanning)
My-T-Soft for Android 2.20.9 (first public release, September 2017)

Notes:

• Depending on product, release version, OS version, and specific technical issue, some tech items are very specific, and some may span to other products/versions
• Downloadable files can also be accessed by anonymous FTP at ftp://downloads.imgpresents.com
• Older files are moved into a separate archive location - see notes/details/new location in *.archived.txt text file

• Return to Technical Support

As seen in ...