diff -r 89d6a7a84779 -r 25a17d01db0c Symbian3/PDK/Source/GUID-581A8E4B-12BE-41C0-A20E-3087A80FEECF.dita
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/Symbian3/PDK/Source/GUID-581A8E4B-12BE-41C0-A20E-3087A80FEECF.dita Fri Jan 22 18:26:19 2010 +0000
@@ -0,0 +1,137 @@
+
+
+
+ There are two types of cases where vibration or audio of the
+device is used as an output method when the user is interacting with the device
+touch screen: When the user has touched an active area of the screen, and an action
+will be triggered on touch release Interaction with given components has been successful As with sounds, tactile feedback must be used carefully so as not to desensitize
+the user to the vibration: the attention grabbing quality remains and functions
+so long as the feedback is not too frequent. Tactile feedback is included in those common UI components, where seen
+as beneficial. When new components are designed, tactile feedback is to be
+included in those if seen beneficial usability-wise. For example, in any button
+type of UI component the tactile feedback is natural. Application can disable
+tactile feedback from the common UI components it uses, if seen necessary.
+This is acceptable only in cases, where tactile feedback would cause interference,
+like during a phone call or when giving audio commands to the system. The user can choose whether tactile feedback is on or off. You can use the following APIs to create
+haptic effects: Tactile
+Feedback Client API available from S60 5.0 onwards can be used on all S60 5.0 or later mobile devices but the feedback
+is played only on touch enabled layouts provides simple functions for triggering various predefined tactile
+feedback (vibration or audio) effects enables a consistent user experience in all applications of the mobile
+device (an application gives a logical feedback type as an input and the actual
+physical effect depends on the mobile device configuration and end user settings) when the area feedback is used, latency is the smallest for the feedback
+triggering (tactile feedback can be triggered at the window server level before
+the corresponding pointer event is delivered to the visible application) direct feedback is easy to integrate into an application can select the logical tactile feedback from certain
+types and the produced effect may be different on various mobile devices Vibra
+API available from S60 3.0 onwards can be used for running device vibrator with given intensity for given
+period of time a privileged client application can use this for playing pulse effects
+which have a really short duration (as the ones used for tactile feedback) You should use Tactile Feedback Client API for providing tactile feedback in custom
+controls (grids, lists, etc.) which comply with the style of the Core UI components
+to ensure a uniform user experience among applications Vibra API to produce haptic effects such as ringing tone vibration
+
+
+
+
+
+
The API to use for tactile
+feedback is the
The Symbian platform includes a tactile
+feedback interface to add, modify and remove feedback areas in the registry.
+There is also an option to trigger direct feedback and bypass the registry.
+
Tactile feedback can be set be disabled in a client +application or a mobile device in some situations, for example, during phone +calls.
Client applications cannot determine the actual physical +feedback that is generated. It depends on device configuration and current +settings. In current devices, the user changeable settings include vibration +and audio feedback intensity level.
In your application, you can use
+the following feedback types, defined in
To use vibration or audio feedback in your application:
Include
Include
To enable +tactile feedback for your application, add the following code.
Do +not delete the pointer in the controller destructor.
To use tactile +feedback when a mobile device user points at a control, add the following +code.
To enable +automatic feedback triggering in a specific area of a UI component, add
Using tactile feedback does not require additional platform +security capabilities for your application.