Home · All Classes · Annotated · Functions

Keypad Architecture

• Introduction
• Keypad Architecture
• Default Scan-codes for Qtopia Keys
• Overriding the Keyboard Handler Qtopia Keys
• Key Behavior in Qtopia
• Keys That Are Always Intercepted
• Keys That Are Sometimes Intercepted

Introduction

Keypad Architecture

For an overview on character input in Qtopia Core see : Character Input.

For a tutorial discussing adding a keyboard driver plugin see : Tutorial: Implementing a Device Plug-in

Default Scan-codes for Qtopia Keys

Nearly all PDAs and Phones have keys that are not found on a regular keyboard. In order for Qtopia to function correctly when installed on a device, it needs these keys to be defined. The easiest way to do this is to have the keyboard driver for the device emit the scancodes for the existing mapping for Qtopia.

In addition to the normal mapping for a US-101 keyboard, the following table sets out the codes that are required / available / optional:

There are two additional keys that do not have default mappings, and should not be used. They are listed below only for reasons of compatibility.

Qtopia is designed to be flexible in terms of the keys required. The default mapping for Qtopia has the following keys:

Note: Qtopia can operate without:

• Key_Call and Key_Hangup
• Key_Left and Key_Right

and Qtopia can operate with Key_Menu rather than Key_Context.

If a device has an alternate button mapping, Trolltech will endeavour to provide assistance in getting Qtopia to work with alternate button mapping.

Overriding the Keyboard Handler Qtopia Keys

If your device does not already have a Qt keyboard driver or it does not emit standard scancodes then a custom Qt keyboard driver will be required.

Drivers can be added by deriving from the QWSMouseHandler and QMouseDriverPlugin classes, or the QWSKeyboardHandler and QKbdDriverPlugin classes, and using Qt's plugin mechanism. See the How to Create Qt Plugins documentation and the Plug & Paint example for details.

Key Behavior in Qtopia

Keys That Are Always Intercepted

Some keys are always intercepted before they reach an application. If a pointer device is available an application can do a keyboard grab to get these keys.

• {Key_F30}
• {Key_F31}
• {Key_F32}
• {Key_F33}
• {Key_F34}
• {Key_F35}
• {Key_NumLock}
• {Key_CapsLock}
• {Key_Menu}
• {Key_Call}
• {Key_Hangup}
• {Key_Flip}

Keys That Are Sometimes Intercepted

• {Key_Escape Rejects active dialog}
• {Key_F33 Accepts active dialog}
• {Key_Back Accepts active dialog}
• {Key_Context1 When behaving as Key_Menu}

While the screen lock is active (SIM card pin required for example) the applications will only be allowed keys such as Key_Back and Key_No. This is to reduce the chance of anyone accessing the phone's data while the SIM-card pin is still required.