Symbian3/SDK/Source/GUID-CBB00F6A-CBA7-4872-B0A1-A86A863725F5.dita
changeset 13 48780e181b38
parent 7 51a74ef9ed63
equal deleted inserted replaced
12:80ef3a206772 13:48780e181b38
     7     Nokia Corporation - initial contribution.
     7     Nokia Corporation - initial contribution.
     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-CBB00F6A-CBA7-4872-B0A1-A86A863725F5" xml:lang="en"><title>Precompiled
    12 <concept id="GUID-CBB00F6A-CBA7-4872-B0A1-A86A863725F5" xml:lang="en"><title>Precompiled resource values available from the Symbian platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    13 resource values available from the Symbian platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    13 <p>The Symbian platform provides a generated resource header file
    14 <p>The Symbian platform provides a generated resource header file that
    14 that contains symbolic IDs to resources in the Symbian platform for
    15 contains symbolic IDs to resources in the Symbian platform for use in your
    15 use in your code. The file with the symbolic IDs is the <parmname>avkon.rsg</parmname> file and it is in the <parmname>./epoc32/include</parmname> folder. The file contains commonly used resource structures for
    16 code. The file with the symbolic IDs is the <parmname>avkon.rsg</parmname> file
    16 your resource file declarations.</p>
    17 and it is in the <parmname>./epoc32/include</parmname> folder. The file contains
    17 <p>A common example is the <parmname>R_AVKON_SOFTKEYS_OPTIONS_EXIT</parmname> symbolic ID, which maps to the <parmname>CBA</parmname> resource
    18 commonly used resource structures for your resource file declarations.</p>
    18 that results in the softkeys <parmname>Options</parmname> and <parmname>Exit</parmname>. The <parmname>Options</parmname> softkey is bound
    19 <p>A common example is the <parmname>R_AVKON_SOFTKEYS_OPTIONS_EXIT</parmname> symbolic
    19 to a command that results in the application framework opening the
    20 ID, which maps to the <parmname>CBA</parmname> resource that results in the
    20 options menu based on the <parmname>MENU_PANE</parmname> resource.
    21 softkeys <parmname>Options</parmname> and <parmname>Exit</parmname>. The <parmname>Options</parmname> softkey
    21 The <parmname>Exit</parmname> softkey returns the <parmname>EAknSoftkeyExit</parmname> command, which would need to be handled in the appropriate place
    22 is bound to a command that results in the application framework opening the
    22 for <xref href="GUID-4941C035-C359-4968-9BD5-31F44EE5F810.dita">command
    23 options menu based on the <parmname>MENU_PANE</parmname> resource. The <parmname>Exit</parmname> softkey
       
    24 returns the <parmname>EAknSoftkeyExit</parmname> command, which would need
       
    25 to be handled in the appropriate place for <xref href="GUID-4941C035-C359-4968-9BD5-31F44EE5F810.dita">command
       
    26 handling</xref> in your application architecture. </p>
    23 handling</xref> in your application architecture. </p>
    27 <note>
    24 <note>
    28 <p>The Symbian platform enumerations are in the <xref href="jar:GUID-759FBC7F-5384-4487-8457-A8D4B76F6AA6.jar!/html/avkon_8hrh.html" format="application/java-archive"><parmname>avkon.hrh</parmname></xref> file,
    25 <p>The Symbian platform enumerations are in the <xref href="jar:GUID-759FBC7F-5384-4487-8457-A8D4B76F6AA6.jar!/html/avkon_8hrh.html" format="application/java-archive"><parmname>avkon.hrh</parmname></xref> file, which is in the <parmname>/epoc32/include</parmname> folder. </p>
    29 which is in the <parmname>/epoc32/include</parmname> folder. </p>
       
    30 </note>
    26 </note>
    31 <p>In general, you can map the commands returned from the CBA options by
    27 <p>In general, you can map the commands returned from the CBA options
    32 comparing the names of the symbolic IDs to the symbolic names in the enumerated
    28 by comparing the names of the symbolic IDs to the symbolic names in
    33 list.</p>
    29 the enumerated list.</p>
    34 <p>Other symbolic IDs for other purposes are also available in the <parmname>avkon.rsg</parmname> file.</p>
    30 <p>Other symbolic IDs for other purposes are also available in
    35 <p>When the precompiled resources fit the needs of your application, you
    31 the <parmname>avkon.rsg</parmname> file.</p>
    36 can use them to access already existing resource structures. </p>
    32 <p>When the precompiled resources fit the needs of your application,
       
    33 you can use them to access already existing resource structures. </p>
    37 <p>For examples of how these symbolic IDs are used, see</p>
    34 <p>For examples of how these symbolic IDs are used, see</p>
    38 <ul>
    35 <ul>
    39 <li><p><xref href="GUID-A3AF142B-F9DF-43FD-9D3F-788A74D0C575.dita">Using
    36 <li><p><xref href="GUID-A3AF142B-F9DF-43FD-9D3F-788A74D0C575.dita">Using
    40 precompiled CBA button resources</xref></p>
    37 precompiled CBA button resources</xref></p></li>
    41 </li>
       
    42 </ul>
    38 </ul>
    43 </conbody></concept>
    39 </conbody></concept>