Viadeo Twitter Google Bookmarks ! Facebook Digg del.icio.us MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Toutes les fonctions  ·  Vues d'ensemble  · 

Qt Bubble Level Example

Files:

Qt Bubble Level is a simple application that uses Qt Mobility's accelerometer APIs and hardware sensor information to calculate the inclination of the device and presents this as atraditional bubble level. The application provides a calibration feature to handle any possible errors in accelerometer readings. The example is hosted in Projects Forum Nokia: https://projects.forum.nokia.com/qtbubblelevel

Note: This demonstration requires QtMobility libraries.

Initialising the application

All of the initialisations are done in the main function.

First, QDeclarativeView is created to intepret the QML files. The QML file given is found in the Qt resource. The root QML element is set to resize to the view whenever the view is resized.

 QDeclarativeView view;
 view.setSource(QUrl("qrc:/qml/BubbleLevel.qml"));
 view.setResizeMode(QDeclarativeView::SizeRootObjectToView);

The Settings object will handle the loading or storing of the calibration value. Next, we create instances from QAccelerometer and AccelerometerFilter and attach the filter to the sensor.

 Settings settings;

 QAccelerometer sensor;
 AccelerometerFilter filter;
 sensor.addFilter(&filter);

The Qt code is then connected to QML code by using Qt Signals and Slots connections. First, the root object is retrieved from QDeclarativeView. The root object now represents the Qt object of the QML root element.

The saveCorrectionAngle signal of the QML root element is connected to the Qt slot saveCorrectionAngle. The rotationChanged and correctionAngle Qt signals are connected to the handleRotation and setCorrectionAngle slot of the QML root element. Finally, the quit signal of QDeclarativeEngine is connected to QApplication's quit slot.

 QObject *rootObject = dynamic_cast<QObject*>(view.rootObject());

 // Associate Qt / QML signals and slots
 QObject::connect(rootObject, SIGNAL(saveCorrectionAngle(const QVariant&)),
                  &settings, SLOT(saveCorrectionAngle(const QVariant&)));

 QObject::connect(&filter, SIGNAL(rotationChanged(const QVariant&)),
                  rootObject, SLOT(handleRotation(const QVariant&)));

 QObject::connect(&settings, SIGNAL(correctionAngle(const QVariant&)),
                  rootObject, SLOT(setCorrectionAngle(const QVariant&)));

 QObject::connect((QObject*)view.engine(), SIGNAL(quit()),
                  &app, SLOT(quit()));

On the Maemo target, the application needs a minimise button, so we connect one additional QML signal to the Qt slot. The minimise button is made visible by setting the value of the QML root element's taskSwitcherVisible property to true.

 #ifdef Q_WS_MAEMO_5
 TaskSwitcher taskSwitcher;

 QObject::connect(rootObject, SIGNAL(minimizeApplication()),
                  &taskSwitcher, SLOT(minimizeApplication()));

 // Show the task switcher button
 rootObject->setProperty("taskSwitcherVisible", true);
 #endif

The correction factor of the accelerometer is retrieved from persistent storage by using QSettings. The correction factor is signalled to the QML side by using the function setCorrectionAngle. The accelerometer sensor is started and it will eventually begin to signal the changes in accelerometer readings.

 // Read correction factor from permanent storage and emit it to QML side
 settings.loadAndEmitCorrectionAngle();

 // Begin measuring of the accelerometer sensor
 sensor.start();

Finally, in the end of the function the view is shown in full screen on mobile devices. On other targets, the application is shown as 800 x 480 resolution in the 100, 100 position from the top-left corner of the desktop.

 #if defined(Q_WS_MAEMO_5) || defined(Q_OS_SYMBIAN) || defined(Q_WS_SIMULATOR)
 view.setGeometry(QApplication::desktop()->screenGeometry());
 view.showFullScreen();
 #else
 view.setGeometry((QRect(100, 100, 800, 480)));
 view.show();
 #endif

Accessing the accelerometer information

The inclination of the device is resolved by using the QAccelerometer sensor of QtMobility. We already created the sensor in the main function and attached our self-derived AccelerometerFilter object to it. Here is the definition of the AccelerometerFilter class:

 #include <QAccelerometerFilter>
 #include <QVariant>

 QTM_USE_NAMESPACE

 class AccelerometerFilter
     : public QObject, public QAccelerometerFilter
 {
     Q_OBJECT

 protected:
     qreal x;
     qreal y;
     qreal z;

 public:
     AccelerometerFilter();
     bool filter(QAccelerometerReading *reading);

 signals:
     void rotationChanged(const QVariant &deg);
 };

The class is multiderived from QObject and QAccelerometerFilter classes. The QAccelerometerFilter class is derived from QObject because we want to use Qt Signals and Slots to signal changes in accelerometer readings.

The members x, y, and z store the previous values of the sensor reading in order to implement a low pass filter to the values.

In the implementation of the AccelerometerFilter class, we first read the value of each axis from the QAccelerometerReading object. The values are then converted from radians to degrees and applied the low pass filter to reduce noise in the sensor readings. Different low pass factors are used depending on the platform (these were determined to be good via experimenting). Finally, the calculated value is emitted.

Note that the accelerometer sensors are oriented differently in Symbian and Maemo devices, and we must account for this by using platform-specific code.

 bool AccelerometerFilter::filter(QAccelerometerReading *reading)
 {
     qreal rx = reading->x();
     qreal ry = reading->y();
     qreal rz = reading->z();

     qreal divider = sqrt(rx * rx + ry * ry + rz * rz);

     // Lowpass factor
 #ifdef Q_OS_SYMBIAN
     float lowPassFactor = 0.10;
 #else
     float lowPassFactor = 0.05;
 #endif

     // Calculate the axis angles in degrees and reduce the noise in sensor
     // readings.
     x += (acos(rx / divider) * RADIANS_TO_DEGREES - 90 - x) * lowPassFactor;
     y += (acos(ry / divider) * RADIANS_TO_DEGREES - 90 - y) * lowPassFactor;
     z += (acos(rz / divider) * RADIANS_TO_DEGREES - 90 - z) * lowPassFactor;

     // The orientations of the accelerometers are different between
     // Symbian and Maemo devices so we use the different axes
     // depending on the platform.
 #if defined(Q_OS_SYMBIAN)
     emit rotationChanged(-y);
 #else
     emit rotationChanged(x);
 #endif

     // Don't store the reading in the sensor.
     return false;
 }

The Qt Quick UI

BubbleLevel.qml is the main QML element. It represents the wooden board of the bubble level, and it also acts as a connection point between the QML and the Qt side. In the beginning of the element, there are two signals, two functions, and one property. All of these define the interface between Qt and QML.

On the Maemo platform, when the application is to be minimised, minimizeApplication is signalled. When a new calibration factor is to be stored in the device's memory, saveCorrectionAngle is signalled.

The handleRotation function acts as a Qt slot to which the AccelerometerFilters signal rotationChanged is connected. Similarly, the setCorrectionAngle function also acts as a Qt slot to which the Settings object's signal, correctionAngle, is connected.

The property alias taskSwitcherVisible is provided to allow the Qt model to show or hide the task switcher button which minimises the application. This is only meaningful on Maemo platforms, where every application normally has a task switcher button.

 // Signaled when task switcher button is pressed
 signal minimizeApplication()

 // Signaled when correction angle is saved
 signal saveCorrectionAngle(variant angle)

 // These functions are used as Qt slots
 function handleRotation(deg) {
     horTube.rawangle = deg
 }

 function setCorrectionAngle(deg) {
     horTube.angleconstant = deg
 }

 // Used to show the task switcher button in Maemo targets
 property alias taskSwitcherVisible: taskSwitcher.visible

The Tube element represents the the glass tube of the bubble level. It is anchored to the centre of the wooden board. The width and height are calculated with specific factors to make the glass tube scale to different resolutions.

 Tube {
     id: horTube

     property real rawangle: 0
     property real angleconstant: 0

     anchors.horizontalCenter: parent.horizontalCenter
     width: parent.width * 0.775; height: parent.height * 0.15625
     deg: rawangle - angleconstant
 }

In the implementation of Tube.qml, the property deg represents the current inclination. The x-position of the bubble is bound to the JavaScript function calX which is called every time the property deg, center, or bubblCenter is changed. The function places the bubble in the corresponding place on its parent.

 Item {
     id: tube

     property real deg

     Image {
         id: bubble

         property real center: tube.width / 2
         property real bubbleCenter: bubble.width / 2

         function calX() {
             var newX = center + tube.deg / -20 * center

             if((newX - bubbleCenter) < 0) {
                 return 0
             }
             else if((newX + bubbleCenter) > tube.width) {
                 return tube.width - 2 * bubbleCenter
             }

             return newX - bubbleCenter;
         }

         x: calX()
         width: 0.16129032 * parent.width; height: 0.66666667 * parent.height
         source: "images/bubble.png"
         smooth: true
     }

     Image {
         anchors.horizontalCenter: parent.horizontalCenter
         width: 0.36451613 * parent.width; height: 0.66666667 * parent.height
         source: "images/scale.png"
     }

     Image {
         width: parent.width; height:  0.32 * parent.height
         opacity: 0.8
         source: "images/reflection.png"
     }
 }
Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 44
  2. Microsoft ouvre aux autres compilateurs C++ AMP, la spécification pour la conception d'applications parallèles C++ utilisant le GPU 22
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. RIM : « 13 % des développeurs ont gagné plus de 100 000 $ sur l'AppWord », Qt et open-source au menu du BlackBerry DevCon Europe 0
  5. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  6. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  7. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
Page suivante

Le Qt Quarterly au hasard

Logo

XQuery et la météo

Qt Quarterly est la revue trimestrielle proposée par Nokia et à destination des développeurs Qt. Ces articles d'une grande qualité technique sont rédigés par des experts Qt. Lire l'article.

Communauté

Ressources

Liens utiles

Contact

  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.7-snapshot
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !
 
 
 
 
Partenaires

Hébergement Web