summaryrefslogtreecommitdiffstats
path: root/doc/src/qtsensors-cpp.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/qtsensors-cpp.qdoc')
-rw-r--r--doc/src/qtsensors-cpp.qdoc16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/qtsensors-cpp.qdoc b/doc/src/qtsensors-cpp.qdoc
index 6740441d..3df97f94 100644
--- a/doc/src/qtsensors-cpp.qdoc
+++ b/doc/src/qtsensors-cpp.qdoc
@@ -68,11 +68,11 @@ sensor.
The life cycle of a QSensor is typically:
\list
-\o Create an instance of QSensor or one of its sub-classes on the stack or heap.
-\o Setup as required by the application.
-\o Start receiving values.
-\o Sensor data is used by the application.
-\o Stop receiving values.
+\li Create an instance of QSensor or one of its sub-classes on the stack or heap.
+\li Setup as required by the application.
+\li Start receiving values.
+\li Sensor data is used by the application.
+\li Stop receiving values.
\endlist
Here is an example of creating a sensor on the heap and on the stack.
@@ -90,9 +90,9 @@ Thanks to Qt's property system you can still access the sensor data. You need to
3 pieces of information in order to do this:
\list
-\o The sensor type.
-\o The property name or index.
-\o The property type or a comparable type.
+\li The sensor type.
+\li The property name or index.
+\li The property type or a comparable type.
\endlist
For example, here is an example of how you can access a property of the accelerometer.