Symbian3/PDK/Source/GUID-7BFEEDF7-3DB8-42FF-9D7A-F98E536F7686.dita
changeset 5 f345bda72bc4
parent 3 46218c8b8afa
child 14 578be2adaf3e
equal deleted inserted replaced
4:4816d766a08a 5:f345bda72bc4
    10 <!DOCTYPE concept
    10 <!DOCTYPE concept
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    12 <concept id="GUID-7BFEEDF7-3DB8-42FF-9D7A-F98E536F7686" xml:lang="en"><title>Sensor
    12 <concept id="GUID-7BFEEDF7-3DB8-42FF-9D7A-F98E536F7686" xml:lang="en"><title>Sensor
    13 interaction</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    13 interaction</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    14 <section id="GUID-27524BA1-FE0E-4906-8A73-C2F8B4B5BC6C"> <p>Devices based
    14 <section id="GUID-27524BA1-FE0E-4906-8A73-C2F8B4B5BC6C"> <p>Devices based
    15 on the Symbian platform are supporting extendable Sensor framework.
    15 on the Symbian platform support extendable Sensor framework. The supported
    16 The supported sensors include accelerometer sensor, which is used for example
    16 sensors include accelerometer sensor, which is used for example for sensing
    17 for sensing device orientation (landscape/portrait and screen down/screen
    17 device orientation (landscape/portrait and screen down/screen up) and short
    18 up) and tapping (giving the device light taps with your hand).  </p> <p>With
    18 tapping on the device with your finger.  </p> <p>With the accelerometer sensor,
    19 the accelerometer sensor, there are three types of interaction that can be
    19 there are three types of interaction that can be achieved:</p><ol>
    20 achieved:</p><ol>
    20 <li id="GUID-E30828C6-4EA8-49B7-BF00-ADC1D132BBFB"><p>Short tapping the device
    21 <li id="GUID-E30828C6-4EA8-49B7-BF00-ADC1D132BBFB"><p>Tapping the device by
    21 by finger to perform a given function in set events. Short tapping the device
    22 hand (double tap) to perform a given function in set events. Tapping the device
    22 interaction is not recommended for touch devices; the user may unintentionally
    23 interaction is not recommended for touch devices: the user may unintentionally
       
    24 tap the device on the touch area, and trigger controls by mistake.</p></li>
    23 tap the device on the touch area, and trigger controls by mistake.</p></li>
    25 <li id="GUID-5700ECF7-40ED-4ECE-ABB5-3C2E93173871"><p>Changing the device's
    24 <li id="GUID-5700ECF7-40ED-4ECE-ABB5-3C2E93173871"><p>Changing the device's
    26 orientation from portrait to landscape and back.</p></li>
    25 orientation from portrait to landscape and back.</p></li>
    27 <li id="GUID-7233626B-2234-44EB-9E64-CB2D787C6CC2"><p>Changing the device
    26 <li id="GUID-7233626B-2234-44EB-9E64-CB2D787C6CC2"><p>Changing the device
    28 orientation from screen down (for example, on a table) to screen up and back
    27 orientation from screen down (for example, on a table) to screen up and back
    29 to perform a given function in set events (for example, silencing an incoming
    28 to perform a given function in set events (for example, silencing an incoming
    30 call).</p></li>
    29 call).</p></li>
    31 </ol><p>In effect, the system is capable of sensing any of these interaction
    30 </ol><p>In effect, the system is capable of sensing any of these interaction
    32 methods in the events where sensors can be used. </p><p>The supported sensor
    31 methods in the events where sensors can be used. </p><p>The supported sensor
    33 interactions are configurable per device. Also, the user can be given the
    32 interactions are configurable per device. Also, the user can be provided with
    34 option to set which one the user would like to use. For example, it is possible
    33 an option to set desired interactions. For example, it is possible to set
    35 to set methods 1 and 3 (double tap by hand and turning the screen downwards)
    34 methods 1 and 3 for the 'Silence incoming call' event. The settings are available
    36 for the Silence incoming call event. The settings are available in Control
    35 in Control Panel.</p><note>When designing an application which uses the sensors,
    37 Panel.</p><note>When designing an application which uses the sensors, take
    36 take into account that the users may switch the use of sensors and display
    38 into account that the users may switch the use of sensors and display orientation
    37 orientation control off in the Control Panel. </note><p>A tap on the device
    39 control off in the Control Panel. </note><p>A double tap on the device produces
    38 produces tactile (vibrating) feedback to reinforce and acknowledge that the
    40 tactile (vibrating) feedback to reinforce and acknowledge that the interaction
    39 interaction has been successful.</p><p>As the Sensor framework is extendable,
    41 has been successful.</p><p>As the Sensor framework is extendable, devices
    40 devices can have different configurations for sensors.  For instance, some
    42 can have different configurations for sensors.  For instance, some devices
    41 devices may have a magnetometer sensors included, which could be then used,
    43 may have a magnetometer sensors included, which could be then used, for example,
    42 for example, as a compass on location-based services.</p><p>For more information,
    44 as a compass on location-based services.</p><p>For more information, see <xref href="GUID-AE979B97-5610-42F3-99A7-5A3D66D3C2E6.dita">Sensor interaction</xref>.</p> 
    43 see <xref href="GUID-AE979B97-5610-42F3-99A7-5A3D66D3C2E6.dita">Sensor interaction</xref>.</p> 
    45    </section>
    44    </section>
    46 </conbody></concept>
    45 </conbody></concept>