🚀 go-pugleaf

Keith R. Bennett <kbennett@access1.digex.net> wrote:
>Where does the KC_VIRTUALKEY flag get set by OS/2 or PM?

By PM.  Non-PM apps don't receive WM_CHAR messages!

In the WM_CHAR message, there are many fields.  One of them, the vKey
field, is used when the key pressed doesn't correspond to a character
in the currently active codepage.  The KC_VIRTUALKEY flag is set when
this field contains valid data.

>Is it a signal or status of the keyboard controller, or does it set
>it if it sees a scan code which it thinks is a virtual key?

The keybaord controller only deal with scan codes and shift masks.
This data is stored in the WM_CHAR message.  The other data, though -
the character and vkey codes - are produced by PM and the keyboard
device driver.

Why do you need to know?  If you need keyboard access in a non-PM
application, you won't be using WM_CHAR messages to do it anyway.

Right now, you have to use DosDevIOCtl functions, stream I/O, or
16-bit APIs to access the keyboard without PM.  The 16-bit Kbd* calls
are probably easiest to use for now.

There are 32-bit equivalents of most of these calls, but you'll need
IBM's Developer's Connection CD to get the headers and documentation
to use them.

-- 
David Charlap        | The contents of this message are not the opinions of
david@visix.com      | Visix Software, or of anyone besides myself.
Visix Software, Inc. +-----------------------------------------------------
Member of Team-OS/2  |
---------------------+