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-8B137691-7C9E-4085-BFFE-4CFE4A64A091" xml:lang="en"><title>Control |
12 <concept id="GUID-8B137691-7C9E-4085-BFFE-4CFE4A64A091" xml:lang="en"><title>Control |
13 pane</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 pane</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
14 <p>The Control pane occupies the bottom part of the screen and displays the |
14 <p>The control pane occupies the bottom part of the screen and displays the |
15 labels associated with the softkeys. </p> |
15 labels associated with the softkeys. </p> |
16 <fig id="GUID-3B64A270-FF5A-4F7E-9D8E-903846944485"> |
16 <fig id="GUID-3B64A270-FF5A-4F7E-9D8E-903846944485"> |
17 <title>Control pane</title> |
17 <title>Control pane</title> |
18 <image href="GUID-A0208BE3-127F-4D04-8045-09C54EF202DD_d0e72845_href.png" placement="inline"/> |
18 <image href="GUID-A0208BE3-127F-4D04-8045-09C54EF202DD_d0e67708_href.png" placement="inline"/> |
19 </fig> |
19 </fig> |
|
20 <note> In landscape orientation, a part of the status pane (the clock and |
|
21 indicator pane) is inside the control pane.</note> |
20 <p>Normal touch down and release functionality applies to the softkeys in |
22 <p>Normal touch down and release functionality applies to the softkeys in |
21 control pane. Activation is performed on touch release. However, activation |
23 control pane. Activation is performed on touch release. However, activation |
22 can be cancelled by dragging the touch from the softkey area and performing |
24 can be cancelled by dragging the touch from the softkey area and performing |
23 a touch release.</p> |
25 a touch release.</p> |
24 <p>The Control pane is also active during <xref href="GUID-BFEEECCA-190B-4DDE-8A04-4FE918BE8690.dita">Options |
|
25 menus</xref>, <xref href="GUID-7B275129-5EF7-4B27-B603-3BDE2C650A93.dita">queries</xref>, |
|
26 and other states using <xref href="GUID-2922758C-37A4-436E-B0F3-358944F84E2A.dita">pop-up |
|
27 windows</xref>, although it does not itself reside in a pop-up window.</p> |
|
28 <p>The actual physical softkeys should be positioned directly beneath the |
26 <p>The actual physical softkeys should be positioned directly beneath the |
29 screen so that the association between the keys and their respective labels |
27 screen so that the association between the keys and their respective labels |
30 is evident. Note, however, that the middle label refers to the Selection key |
28 is evident. Note, however, that the middle label refers to the Selection key |
31 (see <xref href="GUID-2F264A2A-FA7A-4718-A6B6-9A764C1D1E0E.dita">Labeling the Selection |
29 (see <xref href="GUID-2F264A2A-FA7A-4718-A6B6-9A764C1D1E0E.dita">Labeling the Selection |
32 key</xref> for further details).</p> |
30 key</xref> for further details).</p> |
33 <section id="GUID-E372B9B2-8E4A-4D39-8857-CC0A66F9BC75"><title>Using |
31 <section id="GUID-E372B9B2-8E4A-4D39-8857-CC0A66F9BC75"><title>Using |
34 the control pane in C++ applications</title><p>The APIs to use for the control |
32 the control pane in applications</title><p>The APIs to use for the control |
35 pane are the <xref format="html" href="specs/guides/Buttons_API_Specification/Buttons_API_Specification.html" scope="peer">Buttons API</xref> for the softkeys and the <xref format="html" href="specs/guides/Options_Menu_API_Specification/Options_Menu_API_Specification.html" scope="peer">Options menu API</xref> for the menus.</p><p>For implementation |
33 pane are the <xref format="html" href="specs/guides/Buttons_API_Specification/Buttons_API_Specification.html" scope="peer">Buttons API</xref> for the softkeys and the <xref format="html" href="specs/guides/Options_Menu_API_Specification/Options_Menu_API_Specification.html" scope="peer">Options menu API</xref> for the menus.</p><p>For implementation |
36 information on using the softkeys, see <xref format="html" href="specs/guides/Buttons_API_Specification/Buttons_API_Specification.html#Buttons_API_Specification.topic3" scope="peer">Using the Buttons API</xref>. For implementation information |
34 information on using the softkeys, see <xref format="html" href="specs/guides/Buttons_API_Specification/Buttons_API_Specification.html#Buttons_API_Specification.topic3" scope="peer">Using the Buttons API</xref>. For implementation information |
37 on the menus, see <xref format="html" href="specs/guides/Options_Menu_API_Specification/Options_Menu_API_Specification.html#Options_Menu_API_Specification.topic3" scope="peer">Using the Options menu API</xref>.</p><p>The Symbian |
35 on the menus, see <xref format="html" href="specs/guides/Options_Menu_API_Specification/Options_Menu_API_Specification.html#Options_Menu_API_Specification.topic3" scope="peer">Using the Options menu API</xref>.</p><p>The Symbian platform |
38 platform uses Control Button Area (CBA) resources to set the options in the |
36 uses MENU_BAR resources to create the Options menu, when a mobile device user |
39 control pane above the softkeys. CBA resources map the text that appears above |
37 selects the Options softkey. The options that appear above the |
40 the softkeys in the control pane with commands that are collected by the event |
38 softkeys are determined by CBA resources. The MENU_BAR resources map the text |
41 loop of the application framework and delivered to your application for <xref href="GUID-4941C035-C359-4968-9BD5-31F44EE5F810.dita">command handling</xref>.</p><p>When |
39 that appears in the Options menu with commands that are collected by the event |
42 a mobile device user selects an Options softkey, the application framework |
40 loop of the application framework and delivered to your application for command |
43 displays the Options menu based upon the definitions in the menu bar's resources.</p><p>The |
41 handling. </p></section> |
44 Symbian platform uses MENU_BAR resources to create the Options menu, when |
|
45 a mobile device user selects the Options softkey. The options that appear |
|
46 above the softkeys are determined by CBA resources. The MENU_BAR resources |
|
47 map the text that appears in the Options menu with commands that are collected |
|
48 by the event loop of the application framework and delivered to your application |
|
49 for command handling. </p></section> |
|
50 </conbody></concept> |
42 </conbody></concept> |