|  | Home · Overviews · Examples

# Qtopia Core Character Input

When running a Qtopia Core application, it either runs as a server or connects to an existing server. The keyboard driver is loaded by the server application when it starts running, using Qt's plugin system.

Internally in the client/server protocol, all system generated events, including key events, are passed to the server application which then propagates the event to the appropiate client. Note that key events do not always come from a keyboard device, they can can also be generated by the server process using input widgets.

Input Widgets
The server process may call the static QWSServer::sendKeyEvent() function at any time. Typically, this is done by popping up a widget that enables the user specify characters with the pointer device. Note that the key input widget should not take focus since the server would then just send the key events back to the input widget. One way to make sure that the input widget never takes focus is to set the Qt::Tool widget flag in the `QWidget` constructor. The Qtopia environment contains various input widgets such as Handwriting Recognition and Virtual Keyboard.

- Available Keyboard Drivers
- Specifying a Keyboard Driver

## Available Keyboard Drivers

Qtopia Core provides ready-made drivers for the SL5000, Yopy, Vr41XX, console (TTY) and USB protocols. Run the `configure` script to list the available drivers:

        ./configure -help

Note that the console keyboard driver also handles console switching (Ctrl+Alt+F1, ..., Ctrl+Alt+F10) and termination (Ctrl+Alt+Backspace).

In the default Qt configuration, only the "TTY" driver is enabled. The various drivers can be enabled and disabled using the `configure` script. For example:

        configure -qt-kbd-s15000

Custom keyboard drivers can be implemented by subclassing the QWSKeyboardHandler class and creating a keyboard driver plugin (derived from the QKbdDriverPlugin class). Qtopia Core's implementation of the QKbdDriverFactory class will automatically detect the plugin, loading the driver into the server application at runtime.

## Specifying a Keyboard Driver

To specify which driver to use, set the `QWS_KEYBOARD` environment variable. For example (if the current shell is bash, ksh, zsh or sh):

         export QWS_KEYBOARD=<driver>[:<driver specific options>]

The `<driver>` argument are `SL5000`, `Yopy`, `VR41xx`, `TTY`, `USB` and keys identifying custom drivers, and the driver specific options are typically a device, e.g., `/dev/tty0`.

Multiple keyboard drivers can be specified in one go:

         export QWS_KEYBOARD="<driver>[:<driver specific options>]
                 <driver>[:<driver specific options>]
                 <driver>[:<driver specific options>]"

Input will be read from all specified drivers.