diff -r 5072524fcc79 -r 80ef3a206772 Symbian3/PDK/Source/GUID-72DE3EB1-1AF5-4157-8B99-A1C7143DAD2C.dita --- a/Symbian3/PDK/Source/GUID-72DE3EB1-1AF5-4157-8B99-A1C7143DAD2C.dita Fri Jul 02 12:51:36 2010 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,95 +0,0 @@ - - - - - -Navigation -using tabs -

The Symbian user interface uses the tab metaphor that allows combining -several pages of related information into a single state when all of it would -not fit into a single screen or list. The user can switch the tabs using the -Arrow left and Arrow right keys as indicated in the Navi -pane.

- -Navigation using tabs - - -

In this example, state 1-3 uses two tabs to present its information. The -user moves between views 1-3a and 1-3b using the Arrow left and Arrow right -keys. Note that there is no Back function moving between the tab views; Back -from both of them leads to state 1.

-

Tab-controlled views apply the following rules:

- - - Touch interaction model for tabs - - -Default touch -events for tabs - - - - - - -

User action

-

State change

-

Feedback

-
- - - - -

Touch down on a tab

-

No change

-

Highlight is shown.

Tactile: Basic tab effect and audio feedback -are provided with touch down event.

-
- -

Touch down and hold on a tab

-

Inactive

-

Tactile: No effect

-
- -

Touch release on a tab

-

Corresponding view is changed.

Activated tab moves to the -middle of the tab view (all the tabs move along) unless it is the first or -the last tab in the application.

-

Highlight disappears

Tactile: Basic tab effect is provided -with touch release event.

-
- -

Touch down and move horizontally on tab area and release

-

Previous or next tab is opened

-

Tactile: Basic tab effect and audio feedback are provided with touch -down event.

-
- - -
-
Using -tabs in applications

The API to use for tabs is the Tabs API. For implementation information, see Using the Tabs API.

-
\ No newline at end of file