This problem was identified and resolved with an update to the HapticsFeedback.DLL in March 2020 and has been rolled into an update from Zebra Technologies - this is available as part of an update available here: CFE_VC80_W10_RS1_EN_V010400_e_WB (Zebra Portal Logon Required).

Background: The legacy My-T-Soft 1.x software has a different identifying class than the My-T-Soft 2.x software that operates custom layouts. The original HapticsFeedback library did not check for the My-T-Soft 2.x window (custom layout), so never sent physical bezel key event. The update resolves this issue.

For integrators or system administrators, the updated DLL is provided here:

zebravc80hapticslib20200326.zip (20K) March 26, 2020 (MD5: E80C78DD4EE54D6596F776002A8606BA )
NOTE: This download is provided as a convenience for testing/troubleshooting. It is recommended all updates be applied with supported / authorized updates via Zebra Technologies (see link above).

Download/extract zip file - it has one file, the updated HapticsFeedback.DLL

IMPORTANT: Preserve existing DLL file so you can revert to current system if necessary, and then drop in new one:

You will want to rename or backup the existing HapticsFeedback.dll, then unzip downloaded zip file, and drop in the DLL file to the correct location:

C:\Program Files\VCControlPanel\HapticsFeedback.DLL

Do this as Administrator or boot into safe mode to update the HapticsFeedback.DLL - if it is in use, you will not be able to overwrite/update it.

Once updated, you can reset the system, then test. With the original DLL, the physical Bezel keys will not trigger macros when using a custom Build-A-Board layout, but with updated DLL, macros will occur.

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 ...