diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-B05B61B8-1217-441F-BAFA-C209C8F123C5.dita --- a/Symbian3/SDK/Source/GUID-B05B61B8-1217-441F-BAFA-C209C8F123C5.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-B05B61B8-1217-441F-BAFA-C209C8F123C5.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,62 +1,64 @@ - - - - - -Toolbar -APIThe Toolbar API is used for enabling quick access to functions -by displaying them in a toolbar. -

A toolbar contains AVKON buttons. The toolbar supports touch, and can be -with focus or without focus. It contains application-specific buttons (at -least three) that launch application-specific commands. The toolbar content -is application-specific, but you can choose whether the toolbar is displayed -in an application view or not.

-

The Toolbar API supports two types of toolbars: a fixed toolbar for touch -UI, and a floating toolbar which can also be used in non-touch UIs.

- -Fixed toolbar, floating toolbar, and toolbar extension - - -

The fixed toolbar doesn’t have focus, whereas the floating toolbar owns -the focus and it can be used also with navigation and selection keys. By default, -the floating toolbar owns the CBA buttons (Select and Close) -but the floating toolbar can be defined as not having the CBA buttons with -suitable flags.

-

The toolbars are also located differently: a fixed toolbar has a permanent -place in the layout but a floating toolbar can be freely located when it is -defined as having a flexible position.

-

The toolbar extension is a toolbar button that expands the fixed or floating -toolbar. When the extension button is pressed, a grid of toolbar items opens -up. The extension items can be used as actual toolbar items.

-

The extension button itself looks like an ordinary toolbar button. The -only difference is that there is a default icon for the extension button that -is shown if the application does not change the icon itself.

-

For user experience guidelines on the toolbar component, please see the toolbar UI component description.

-

For information -on using the API, see Enabling -quick access to functions with a toolbar.

For the Toolbar API -classes and header files, see Classes and Definitions.

-
Constraints

This -API is valid for all platforms running on Symbian OS v9.3 or later.

-
Emulator support

This -API is supported in the WINS/WINSCW emulator environment, with the following -exception:

    -
  • Tactile feedback is not supported.

  • -
-
-Related APIs -Generic button -API - for creating toolbar buttons - -Form API - for including editable fields in fixed toolbar extensions - - + + + + + +Toolbar +APIThe Toolbar API is used for enabling quick access to functions +by displaying them in a toolbar. +

A toolbar contains AVKON buttons. The toolbar supports touch, and can be +with focus or without focus. It contains application-specific buttons (at +least three) that launch application-specific commands. The toolbar content +is application-specific, but you can choose whether the toolbar is displayed +in an application view or not.

+

The Toolbar API supports two types of toolbars: a fixed toolbar for touch +UI, and a floating toolbar which can also be used in non-touch UIs.

+ +Fixed toolbar, floating toolbar, and toolbar extension + + +

The fixed toolbar doesn’t have focus, whereas the floating toolbar owns +the focus and it can be used also with navigation and selection keys. By default, +the floating toolbar owns the CBA buttons (Select and Close) +but the floating toolbar can be defined as not having the CBA buttons with +suitable flags.

+

The toolbars are also located differently: a fixed toolbar has a permanent +place in the layout but a floating toolbar can be freely located when it is +defined as having a flexible position.

+

The toolbar extension is a toolbar button that expands the fixed or floating +toolbar. When the extension button is pressed, a grid of toolbar items opens +up. The extension items can be used as actual toolbar items.

+

The extension button itself looks like an ordinary toolbar button. The +only difference is that there is a default icon for the extension button that +is shown if the application does not change the icon itself.

+

For user experience guidelines on the toolbar component, please see the toolbar UI component description.

+

For information +on using the API, see Enabling +quick access to functions with a toolbar.

For the Toolbar API +classes and header files, see Classes and Definitions.

+
Changes and release information

The Toolbar API +is an SDK API and first released in S60 5th Edition.

+
Constraints

This +API is valid for all platforms running on Symbian OS v9.3 or later.

+
Emulator support

This +API is supported in the WINS/WINSCW emulator environment, with the following +exception:

    +
  • Tactile feedback is not supported.

  • +
+
+Related APIs +Generic button +API + for creating toolbar buttons + +Form API + for including editable fields in fixed toolbar extensions + +
\ No newline at end of file