Creating Custom Key Maps For The Vx6; Introduction - Honeywell VX6 Reference Manual

Creating Custom Key Maps for the VX6

Creating Custom Key Maps for the VX6
Prerequisite:
Note:

Introduction

A command-line compiler called KEYCOMP.EXE is provided on the SDK CD. Using this
compiler, the System Administrator can convert a sample default key map text file into a custom
key map text file which, when loaded onto the VX6, can be chosen by the user to replace the
default VX6 keymap and then switched back when they are finished using the customized keys.
This custom key map file can be made to re-define the system return code for each of the 61 keys,
key press or key press combinations. All keys, except the power key, can be re-mapped.
Custom keymaps for the VX6 are created on a desktop PC using the command line compiler
KEYCOMP.EXE. Keycomp processes the input keymap source file and outputs a registry text
file.
Note:
Example:
DEFAULT.KEY
This output file should be renamed to xxx.REG (the suffix must remain REG), then copied to the
VX6 over ActiveSync. Once the file is loaded on the VX6, double-click the file from the
Windows CE Explorer desktop. This will run the REGLOAD utility to put it into the registry, and
save the registry to non-volatile flash. The keymap is now a permanent part of the VX6, and the
REG file is no longer needed unless it is necessary to perform a cold boot; this will return the
registry to factory defaults, and it will be necessary to double-click the REG file again.
Once the keymap has been added to the registry, it should appear in the Keyboard control panel,
in the Keymap popup menu. To activate the keymap, select the keymap from the popup menu, and
close the control panel with the OK button. To return to the default keymap, select Preload or
0409 (depending on system software revision) from the keymap popup and click OK.
The compiler has three functional stages:
E-EQ-VX6RG-F
LXE SDK CD
Since the VX6 does not contain an integrated scanner, the VX6 does not have scan keys
on the keyboard. Likewise, any scan key that is programmed will not operate a tethered
scanner attached to the VX6.
Each VK_code has a numeric value (for example, VK_F20 = hex 83), these are
documented in the SDK include file WINUSER.H (from Microsoft). The numeric value is
what needs to go into the registry. Whether the value is hex or decimal depends on the
registry editor being used - the one in the VX6 requires decimal, but the desktop one used
over ActiveSync that a developer may use requires hex.
KEYCOMP DEFAULT.KEY
Input File
•
First, the input file is read and parsed for any syntax errors. The data read is stored in
internal tables.
•
Second, the data parsed from the input file is validated to see that all of the items
required by the keyboard driver for normal operation are present.
•
Third and finally, the KEYCOMP.REG file is written out in the format required by
the REGLOAD utility on the Windows CE device.
(writes KEYCOMP.REG to local directory)
Compiler
KEYCOMP.EXE
285
Text File
KEYCOMP.REG
VX6 Reference Guide