diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-0D093C3D-4D85-455E-B685-064A9B25B1FE.dita --- a/Symbian3/SDK/Source/GUID-0D093C3D-4D85-455E-B685-064A9B25B1FE.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-0D093C3D-4D85-455E-B685-064A9B25B1FE.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,107 +1,107 @@ - - - - - -Touch -UI user experience -

In general, the touch UI in the Symbian platform devices emulates the functionality -of the Arrow and Selection keys, but there are many deviations to this general -principle. Touch interaction design is a success if mobile device users choose -to use the stylus or finger even if all the same tasks can be performed using -the hardware keys. All Symbian platform common components are touch-enabled, -allowing full use with a finger.

-

The touch UI is designed to enable full task flow with touch, without the -need to switch to hardware keys. Thus, the design ensures that users can complete -a task with the chosen interaction method (keys or touch) from start to finish. -However, the touch UI offers some usability benefits compared to keyboard -use.

-

The following guidelines must be followed while designing applications -for touch use:

- -

In touch interaction, touch refers to pressing the finger or stylus against -the touch screen, tap corresponds to touch and release, while touch and drag -means touching and moving the finger or stylus along the screen. Basic touch -interaction is achieved through a short tap and long tap. In the short tap, -users place down and lift up a finger on the same item within a short period -of time. A long tap performs some specific actions (described in more detail -in Touch down and hold) -when users hold down the finger on a component for a set amount of time. The -following table lists the actions that take place on various finger movements.

-

The touch and drag functionality is not supported by Symbian platform -as an integrated part of the style, but it is supported in some selected applications -such as moving items in the Menu.

 -Touch events - - - -Touch type -Description - - - - -

Touch

 -

The following actions take place on touch:

    -

  • The component or control under the finger takes active focus.

    • -

  • The button under the finger changes its appearance to the pressed down -status.

    • -

  • Scrolling is activated if the finger is on a scrollbar.

    • -
 - - -

Tap

 -

The following actions take place on a tap (touch and release):

    -

  • The menu command under the finger is activated.

    • -

  • The button that was pressed down is released and the corresponding -function is performed (unless it is a latching button as in a toolbar).

    • -
 - - -

Touch and cancel

 -

Users can cancel any action on the objects on which they place the -finger by dragging the finger outside the object area before lifting it. If -the users drag the finger back onto the object before they lift it, the action -is performed.

 - - -

Touch and drag

 -

Users can place the finger on the screen and move it on the screen -without lifting it. This kind of dragging can be used to:

    -

  • Scroll lists and grids.

    • -

  • Select multiple objects in lists (see Touch -based multiple selection).

    • -

  • Browse menu items. When the finger moves on a menu item, the item is -focused and opens possible submenu panes. Lifting the finger performs the -focused menu command.

    • -

  • Highlight text in appropriate editor fields (paint it).

    • -

  • Perform application-specific functions, such as drawing lines or dragging -selections.

    • -
 - - - -
-
Using -touch events in C++ applications

For information on how to receive -touch events using application -and UI frameworks , see Window -server events and Pointer -events.

+ + + + + +Touch +UI user experience +

In general, the touch UI in the Symbian platform devices emulates the functionality +of the Arrow and Selection keys, but there are many deviations to this general +principle. Touch interaction design is a success if mobile device users choose +to use the stylus or finger even if all the same tasks can be performed using +the hardware keys. All Symbian platform common components are touch-enabled, +allowing full use with a finger.

+

The touch UI is designed to enable full task flow with touch, without the +need to switch to hardware keys. Thus, the design ensures that users can complete +a task with the chosen interaction method (keys or touch) from start to finish. +However, the touch UI offers some usability benefits compared to keyboard +use.

+

The following guidelines must be followed while designing applications +for touch use:

+
    +

  • Design decisions must be based on the real-time use cases.

    • +

  • Enable touch functionality only for obvious functions to make sure +that users can find them.

    • +

  • Keep in mind that not every item on the screen has to have a functionality +attached to it and that the functionality should not be too surprising or +radical.

    • +

  • Keep in mind that theme design alone is not sufficient as means of +indicating touch functionality; where one theme may indicate touch, another +may not.

    • +
+

In touch interaction, touch refers to pressing the finger or stylus against +the touch screen, tap corresponds to touch and release, while touch and drag +means touching and moving the finger or stylus along the screen. Basic touch +interaction is achieved through a short tap and long tap. In the short tap, +users place down and lift up a finger on the same item within a short period +of time. A long tap performs some specific actions (described in more detail +in Touch down and hold) +when users hold down the finger on a component for a set amount of time. The +following table lists the actions that take place on various finger movements.

+

The touch and drag functionality is not supported by Symbian platform +as an integrated part of the style, but it is supported in some selected applications +such as moving items in the Menu.

 +Touch events + + + +Touch type +Description + + + + +

Touch

 +

The following actions take place on touch:

    +

  • The component or control under the finger takes active focus.

    • +

  • The button under the finger changes its appearance to the pressed down +status.

    • +

  • Scrolling is activated if the finger is on a scrollbar.

    • +
 + + +

Tap

 +

The following actions take place on a tap (touch and release):

    +

  • The menu command under the finger is activated.

    • +

  • The button that was pressed down is released and the corresponding +function is performed (unless it is a latching button as in a toolbar).

    • +
 + + +

Touch and cancel

 +

Users can cancel any action on the objects on which they place the +finger by dragging the finger outside the object area before lifting it. If +the users drag the finger back onto the object before they lift it, the action +is performed.

 + + +

Touch and drag

 +

Users can place the finger on the screen and move it on the screen +without lifting it. This kind of dragging can be used to:

    +

  • Scroll lists and grids.

    • +

  • Select multiple objects in lists (see Touch +based multiple selection).

    • +

  • Browse menu items. When the finger moves on a menu item, the item is +focused and opens possible submenu panes. Lifting the finger performs the +focused menu command.

    • +

  • Highlight text in appropriate editor fields (paint it).

    • +

  • Perform application-specific functions, such as drawing lines or dragging +selections.

    • +
 + + + +
+
Using +touch events in applications

For information on how +to receive touch events using application +and UI frameworks , see Window +server events and Pointer +events.

 \ No newline at end of file