diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-76FD2A71-E8A3-4C82-9704-3F7F6AD4DFD8.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-76FD2A71-E8A3-4C82-9704-3F7F6AD4DFD8.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,138 @@ + + + + + +Navi +pane +

The principal uses of the Navi pane are to display information about the +current state and view, and to help the user to navigate in the application.

+ +Navi pane + + +

Depending on the context, the Navi pane contains elements presented in +the following table.

+Possible Navi +pane content + + + +Component +Description + + + + +

Tabs

+

Tabs are used to view parallel data views alternatively. Arrow indicators +are shown at both ends of the pane when there are further tabs to scroll in +the corresponding direction. Each tab has either a graphic or a text (or both) +as a label. The following tab layouts can be used:

    +
  • Two tabs

  • +
  • Three tabs

  • +
  • Four tabs

  • +
  • Two long tabs

  • +
  • Three long tabs (stacked so that only one is fully visible at a time)

  • +
The currently active tab is highlighted.

More than four tabs can +exist simultaneously. They can be scrolled horizontally. However, as a design +guideline, the number of tabs should be kept small (the maximum of six tabs +is recommended), and the number should not be dynamic. See Navigation +using tabs for +a description of the effect of tabs on the navigation within an application.

+
+ +

Navigation text (icon+text)

+ +
+

Navigation text is displayed in the Navi pane when +similar items can be browsed by scrolling horizontally, such as dates in Calendar. +Arrow indicators at both ends of the pane indicate the possibility to scroll.

+
+ +

Indicators

+ +
+

In editors, the Navi pane contains editing +indicators. See Indicators for +a more detailed description of the Navi pane indicators.

+
+ +

Folder structure indication

+ +
+

Opened subfolders are indicated in the Navi pane.

+
+ +

Application-specific content

+

When none of the above content types is suitable, the Navi +pane content can be designed specifically for an application.

+
+ + +

Empty pane

+ +
+

The Navi pane can be empty.

+
+ + +
+

+Default touch +events for ungrouped soft notification + + + + + + +

User action

+

State change

+

Feedback

+
+ + + +

Touch down on navigation text or navigation arrow

+

Application specific

+

Tactile: In case of activity, basic button effect and audio feedback +is provided.

+
+ +

Touch down and hold on navigation text

+

Inactive

+

Tactile: No effect

+
+ +

Touch down and hold on arrows

+

This action performs a “key repeat”, similar to many touch downs +and releases on arrow

+

Tactile: Sensitive button effect and audio feedback is provided +with key repeat action.

+
+ +

Touch release

+

No effect

+

Tactile: No effect

+
+ + +
+

Using +the navi pane in C++ applications

The API to use for the Navi pane +is the Navigation pane API. If you use tabs in the Navi pane, +the API for controlling the tabs is the Tabs API.

For the indicators in the Navi pane, use +the Indicators API.

For implementation information on the Navi pane, +see Using the Navigation pane API. For implementation information +on tabs, see Using the Tabs API.

The class MAknNaviDecoratorObserver provides touch support +for the tab arrows in the Navi pane. To set the observer, use the method CAknNavigationDecorator::SetNaviDecoratorObserver().

To create a tab group in the Navi pane, use the +method CreateTabGroupL() in the class CAknNavigationControlContainer. This is a factory +method for a pre-implemented navigation pane tab group control.

+
\ No newline at end of file