Interaction -with other hardware components

In addition to traditional keys, interaction devices of other types may -be built in the devices. In most scenarios, they produce input events similar -to keys, so that the software need not be changed. The hardware commands do -not have any effect on the application.

Examples of specific interaction devices are:

Optical joysticks
Optical 9-way finger navigation
Acceleration sensors

Optical joystick

An optical joystick can be used -instead of (or in addition to) the traditional navigation keys.

When -used in combination with traditional scroll keys, optical joystick performs -same functions as that of mechanical scroll keys. However, the speed of the -movement can differ.

When used individually as the only scrolling device, -optical joystick emulates the functions of mechanical scroll keys. Sliding -a finger down over the joystick provides the same function as that of pressing -the down key. Repeat functionality can be produced with longer strokes.

Optical -9-way navigation

The Symbian platform supports additional optical -navigation that is integrated to centre Select key. The supported directions -in 9-way rocker key are domed main directions and diagonals by combining the -main directions. Optical navigation allows continues moment of the finger -as observed in touch pad. It is suitable for pointer moving in browser and -content panning, for example, in photos, browser, and maps.

Acceleration -sensor

There are three types of interaction events that can be recognized -with acceleration sensors:

Tapping the device by -hand (double tap) to perform a given function in set events. Tapping interaction -is not recommended for touch devices to prevent the unintentional touch actions.
Changing the device’s -orientation from portrait to landscape and back to perform screen re-orientation.
Changing the device -orientation from screen up (for example on a table) to screen down and back -to silence an alert tone (for example, silencing an incoming call).

The system is capable of sensing any of listed events. The supported -sensor interactions are configurable per device, but must be consistent in -not assigning different functions to these standard events. Also, the user -can be provided with the option to set the desired interactions. For example, -it is possible to set methods 1 and 3 (double tap by hand and turning the -screen downwards) for the 'silence incoming call' event. The settings are -available in General Settings. A double tap on the device produces -tactile (vibrating) feedback to reinforce and acknowledge that the interaction -is successful. See Tactile -feedback for more details.