Message Constants¶
Input Device Event Messages¶
Pointing Device Event Messages¶
MOUSE()
MOUSE()
MOUSE()
Note that a pointing device isn’t expected to send the
B_MOUSE_ENTER_EXIT
message.
Keyboard Device Event Messages¶
B_KEY_DOWN
B_UNMAPPED_KEY_DOWN
B_KEY_UP
B_UMAPPED_KEY_UP
B_MODIFIERS_CHANGED
Input Device Control Messages¶
Pointing Device Control Messages¶
Constant |
Description |
---|---|
|
Requests that the receiver change the mouse double-click speed to the value retrieved through |
|
Requests that the receiver change the mouse map (the correspondence between physical mouse buttons and the |
|
Requests that the receiver change the mouse speed to the value retrieved through |
|
Requests that the receiver change the mouse type (the number of buttons) to the type retrieved through |
Keyboard Device Control Messages¶
Constant |
Description |
---|---|
|
Requests that the receiver change the state of the locked keys (caps lock, num lock, etc.). To get the desired state of the locking keys, read the states out of the key map returned by |
|
Requests that the receiver change the keyboard’s key map—the mapping between physical keys and the character codes they generate. The new key map is returned by |
|
Requests that the receiver change the delay before a held key starts generating repeated characters to the value retrieved through |
|
Requests that the receiver change the speed at which a held key generates repeated characters to the value retrieved through |
Device Monitoring¶
The input()
function lets you ask the Input Server to send
you a message when a device starts or stops, or when the set of
registered devices changes. These “device monitoring” notifications are
sent to the target specified in the function. The command constant is
always B_INPUT_DEVICES_CHANGED.
The be:opcode field will be one of:
Constant |
Description |
---|---|
|
An input device has been added to the system. |
|
An input device has been removed from the system. |
|
An input device has been started. |
|
An input device has been stopped. |
Input Method Events¶
Active input methods send input method events
(B_INPUT_METHOD_EVENT
messages) downstream to application views to help integrate the method’s
work with the view’s display. Inside each
B_INPUT_METHOD_EVENT
message is
a be:opcode field indicating the type of
input method event:
Constant |
Description |
---|---|
|
Sent whenever the user changes the text during an input transaction. |
|
Sent whenever the input method needs to know the on-screen locations of characters in the input transaction. |
|
Sent when a new input transaction is beginning. |
|
Sent when an input transaction is completed. |