diff -r 89d6a7a84779 -r 25a17d01db0c Symbian3/PDK/Source/GUID-E402616A-7ED8-45AC-B836-99C3A3760B33.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/PDK/Source/GUID-E402616A-7ED8-45AC-B836-99C3A3760B33.dita Fri Jan 22 18:26:19 2010 +0000 @@ -0,0 +1,46 @@ + + + + + +Key events +Key presses generate key events +

Key events are generated when a mobile device user presses one or more +mobile device key buttons. The application framework delivers the event to +the application that has focus. The TKeyEvent structure +is used to contain the key event details delivered to the application. For +more information on TKeyEvent, see TKeyEvent.

+

The structure is as follows:

+struct TKeyEvent + { + TUint iCode; + TInt iScanCode; + TUint iModifiers; // State of modifier keys + TInt iRepeats; // Count of auto repeats generated + }; + +

The following events are generated by means of a single key press and +release:

+EEventKeyDown +EEventKey +EEventKeyUp + + +

The first event indicates that a key has been pressed down. The second +event indicates that a character has been received from the keyboard. The +third event is sent when the button has been released. These events are described +in the iCode and iSCanCode members +of TKeyEvent.

+

For more information on possible data contained in EEventKey, +see TKeyCode.

+

Key presses may be interpreted by a Front End Processor (FEP) and tied +to specific key events. For example, if a mobile device user presses the 2 key +twice, an active FEP could generate a key event code of b.

+

For more information on FEPs, see Front End Processor overview.

+
\ No newline at end of file