|
|
This status indicate that either the left-Alt key or the right-Alt key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the CapsLock key was locked when the key or mouse message posted to the window. You can test the status by AND'ed with lParam of the message, like below
switch (message) { case MSG_KEYDOWN: if (lParam & KS_CAPSLOCK) { // the CapsLock key is locked. ... } break; ...
|
|
|
This status indicate that the mouse is captured by a window when the mouse message posted. You can test the status by AND'ed with lParam of the message, like below:
switch (message) { case MSG_MOUSEMOVE: if (lParam & KS_CAPTURED) { // the mouse is captured by this window. ... } break; ...
|
|
|
This status indicate that either the left-Ctrl key or the right-Ctrl key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the key message is posted by the IME window.
|
|
|
This status indicate that left-Alt key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that left button was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the left-Ctrl key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that left-Shift key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that middle button was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the NumLock key was locked when the key or mouse message posted to the window.
|
|
|
This status indicate that the key down message is an auto-repeated one. You can test the status by AND'ed with lParam of the message, like below:
switch (message) { case MSG_KEYDOWN: if (lParam & KS_REPEATED) { // the key down messsage is auto-repeated. ... } break; ...
|
|
|
This status indicate that right-Alt key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that right button was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the right-Ctrl key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that right-Shift key was pressed when the key or mouse message posted to the window.
|
|
|
This status indicate that the ScrollLock key was locked when the key or mouse message posted to the window.
|
|
|
This status indicate that either the left-Shift key or the right-Shift key was pressed when the key or mouse message posted to the window.
|
|
|
The mask of mouse button status.
|
|
|
The mask of key status.
|
|
|
Number of MiniGUI keys. The number of MiniGUI keys is defined to 255 by default. This means that MiniGUI can destinguish 255 different keys with each has an unique scan code. The scan codes below 129 are defined for PC keyboard by default. If your system has a large amount of keys, you can define the scan code of keys ranged from 1 to 255 in your IAL engine. And your application will receive a MSG_KEYDOWN and MSG_KEYUP messages when a key pressed and released, and the wParam of the messages will be defined to be equal to the scan code of the key.
|
|
|
The number of keys defined by Linux operating system. For a PC box, NR_KEYS is defined to 128 by default. You can define some input events from an input device other than keyboard, e.g. your remote controller, as key events with different scan codes from those of PC's. MiniGUI can support 255 keys, and the constant is defined by MGUI_NR_KEYS.
|
|
|
The first key scan code different from OS defined ones. You can define your special key scan codes like below
#define SCANCODE_PLAY (SCANCODE_USER) #define SCANCODE_STOP (SCANCODE_USER + 1) #define SCANCODE_PAUSE (SCANCODE_USER + 2) to distinguish the keys on your remote controller.
|
1.4.2