Symbian3/SDK/Source/GUID-E402616A-7ED8-45AC-B836-99C3A3760B33.dita
changeset 8 ae94777fff8f
parent 7 51a74ef9ed63
child 13 48780e181b38
equal deleted inserted replaced
7:51a74ef9ed63 8:ae94777fff8f
     8 Contributors: 
     8 Contributors: 
     9 -->
     9 -->
    10 <!DOCTYPE concept
    10 <!DOCTYPE concept
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    12 <concept id="GUID-E402616A-7ED8-45AC-B836-99C3A3760B33" xml:lang="en"><title>Key events</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    12 <concept id="GUID-E402616A-7ED8-45AC-B836-99C3A3760B33" xml:lang="en"><title>Key events</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    13 <fig id="GUID-9A1FDF4B-5FD8-4113-8D8E-E879B4C7C255"><title>Key presses generate key events</title><image href="GUID-C9429505-EEE7-4E64-BE0A-BC5D57D5B42C_d0e42810_href.png"/></fig>
    13 <fig id="GUID-9A1FDF4B-5FD8-4113-8D8E-E879B4C7C255"><title>Key presses generate key events</title><image href="GUID-C9429505-EEE7-4E64-BE0A-BC5D57D5B42C_d0e37243_href.png"/></fig>
    14 <p>Key events are generated when a device user presses one or more device
    14 <p>Key events are generated when a device user presses one or more device
    15 key buttons. The application framework delivers the event to the application
    15 key buttons. The application framework delivers the event to the application
    16 that has focus. The <parmname>TKeyEvent</parmname> structure is used to contain
    16 that has focus. The <parmname>TKeyEvent</parmname> structure is used to contain
    17 the key event details delivered to the application. For more information on <parmname>TKeyEvent</parmname>,
    17 the key event details delivered to the application. For more information on <parmname>TKeyEvent</parmname>,
    18 see <xref href="GUID-0F8FA6A3-F172-36E4-9CF5-60814ABCD562.dita"><apiname>TKeyEvent</apiname></xref>. </p>
    18 see <xref href="GUID-0F8FA6A3-F172-36E4-9CF5-60814ABCD562.dita"><apiname>TKeyEvent</apiname></xref>. </p>
    40 <p>For more information on possible data contained in <parmname>EEventKey</parmname>,
    40 <p>For more information on possible data contained in <parmname>EEventKey</parmname>,
    41 see <xref href="GUID-B67B6ED5-6C8F-3B36-934C-B47A109A515F.dita"><apiname>TKeyCode</apiname></xref>.</p>
    41 see <xref href="GUID-B67B6ED5-6C8F-3B36-934C-B47A109A515F.dita"><apiname>TKeyCode</apiname></xref>.</p>
    42 <p>Key presses may be interpreted by a Front End Processor (FEP) and tied
    42 <p>Key presses may be interpreted by a Front End Processor (FEP) and tied
    43 to specific key events. For example, if a device user presses the <parmname>2</parmname> key
    43 to specific key events. For example, if a device user presses the <parmname>2</parmname> key
    44 twice, an active FEP could generate a key event code of <parmname>b</parmname>.</p>
    44 twice, an active FEP could generate a key event code of <parmname>b</parmname>.</p>
    45 <p> For more information on FEPs, see <xref href="GUID-FCEDC338-61CA-5D10-A8DB-E44A3EBBDE5E-GENID-1-8-1-3-1-1-9-1-3-1.dita">Front
    45 <p> For more information on FEPs, see <xref href="GUID-FCEDC338-61CA-5D10-A8DB-E44A3EBBDE5E.dita">Front
    46 End Processor overview</xref>.</p>
    46 End Processor overview</xref>.</p>
    47 </conbody></concept>
    47 </conbody></concept>