The purpose of
this branch is to allow clients to render POS keyboards and to
label the key switches.
There are several
factors that must be identified before a keyboard layout can be
drawn:
What is the type of
the keyboard?
What 4690 keyboard
definition record is in use for the terminal?
What input state table
is in use for the running terminal application?
What labels does a
given retailer use for the function codes that are defined in the
keyboard layout?
Finally, what other
attributes go with the label (e.g. color, help text, etc).
When a client
gets ready to render a keyboard, its steps might be:
1.
Decide which
terminal to monitor
2.
Determine the
type of keyboard in use at that terminal
3.
Determine the
active input state table for the terminal
4.
Determine if the
application already has keyboard labeling information saved locally
for the terminal/keyboard/state table.
If so, determine
if local information is still valid (by checking
qsa4690KeyboardDefsGlobalUniqueID).
5.
If local
information needs to be refreshed, retrieve label information for
all key switches using qsa4690KeyboardDefsPerKeyTable.
| Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |