| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
needed for automatic static linking (and later deployment).
the gesture plugins are excluded from the automation based on the
assumption that they are usually not needed.
the example and the test plugin are also excluded for obvious reasons.
Change-Id: I7645aa0daf216ce430989e13d4380dbe6dd2bbd1
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The plugin key for both the Generic backend and the BlackBerry backend
were set to "notused". This ultimately caused the Generic backend not
to be loaded, which is why QTiltSensor wasn't being exposed. The duplicate
keys caused a collision in a QMap in QFactoryLoader, making it look
like the generic backend had been created, when it hadn't.
Tested on a BlackBerry Z10.
Change-Id: Ie5e40586751e7c3b9683a94a39b07efd4fc7fc82
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There is no need for the CONFIG+=simulator logic anymore.
qtHaveModule() is an automatic way of doing the same.
Change-Id: Ibe87abb93e036a82fae3a752d9886c58ccebeec1
Reviewed-by: Rainer Keller <rainer.keller@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|\|
| |
| |
| | |
Change-Id: I6b203a32b2f52255ae4e63cfb279e762458c0128
|
| |
| |
| |
| |
| |
| |
| |
| | |
Also, this brings the front page layout somewhat further
in line with qtlocation & qtconnectivity API docs.
Change-Id: I5e54ae388892dcb2a806c4775828abcdc81eb79d
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create a new sensor type for distance. This sensor type supports new hardware sensors
that can measure physical distance from the device, in centimeters. The API is designed
to mimic the Android API for proximity (TYPE_PROXIMITY), so that if a given proximity
sensor only supports a binary measurement (near vs far), then instead of reporting distance
in cm, the QDistanceSensor will return the max range value to represent far, and a lesser
value to represent close. Using this definition should simplify implementation.
The main reason for not implementing this as a new property of QProximitySensor is that
clients of QProximitySensor have made the assumption that they will receive the readingReady
signal if and only if the reading has changed from near to far or vice versa. Adding a
distance property will break that assumption, as distance has a higher degree of precision.
Change-Id: Ia804948c78ff7391fc8b78df975cddcf861326dc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Qt API does not expose Linear Accel and Gravity as separate sensor types,
they are different versions of QAccelerometer, accessed by modifying the
accelerationMode property. The possible values are Combined, User, and Gravity, which
correspond to Acceleration, Linear Acceleration, and Gravity respectively. When
constructing the accelerometer backend, the accelerationMode must be queried. The
backend must also connect to the accelerationModeChanged signal from the QAccelerometer.
I think that the existing implementation of QSensors on Android assumes that there is a
one-to-one correspondence between QSensors and AndroidSensorTypes. To fix this assumption,
I promoted the m_type attribute of androidcommonsensor.h from private to protected so
that a sensor backend can update the Android sensor being used.
Task-number: QTBUG-30531
Change-Id: I842d2485109542f74731d179e2720ea55fa248cc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
| |
Change-Id: I4754a36bd6977cc2bc83a3fee58fb5ce6d2c2c84
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
The current algorithm for close detection in QProximitySensor will not
work for sensors whose output is not binary (ie, close/far). The new
algorithm will use the threshold of 8cm when the output is not binary.
Change-Id: I2173e9afae0a2d29434e092e1afc09d1c6f5647c
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
|
|
|
|
|
| |
Change-Id: I8541601c0bfe2b7c80e88b4617e8215b266fb0bd
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
|
|
|
| |
Change-Id: If01a988c151ec696c8d02ca7c470d7e97a593b40
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
|
|
|
|
| |
This provides the sensor plugin with support for accelerometer,
gyroscope, rotation sensor, orientation sensor, compass, and
ambient light sensor.
Change-Id: Ic91a6cef98e4011858552c5cd6407b494579fe17
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
| |
Profiling shows Qt Creator spends 2% of its load time normalizing
Change-Id: I462d0e0b603ab644e57c5b804015508abeebdc6e
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
| |
Change-Id: Ifc7b86fa4d40dd051399999ad998b0750183d501
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Oliver Wolff <oliver.wolff@digia.com>
|
|
|
|
|
|
| |
Change-Id: I09b5df218ad22afefe8a615c80585aa3fb46006f
Reviewed-by: Robin Burchell <robin+qt@viroteck.net>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
| |
Change-Id: I5639fb872b8e41cc5c5b5968cf1ddf7e247961e2
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
|
| |
This patch aims to make QtSensors uses Q_DECL_OVERRIDE uniformly across
the module
Task-number: QTBUG-27392
Change-Id: I5f814f93307159175f92e29a9990587c03cce96f
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 5.2, the HTML output is in a flatter structure and when they are
hosted in qt-project.org/doc, the documentation will be found at
http://qt-project.org/doc/qt-$QT_VER
The url variable is used by projects outside of Qt 5 which need
to link to Qt 5 documentation, such as Qt Creator.
Task-number: QTBUG-34584
Change-Id: Id4428de7ea0a7a4f7dd7a28d76927195c61755ce
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
Minor corrections in compatmap.qdoc
Task-number: QTBUG-32173
Change-Id: Ic4f881449e65c2d6889f0e217d251214997a8a56
Reviewed-by: Martin Smith <martin.smith@digia.com>
Reviewed-by: Laszlo Papp <lpapp@kde.org>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|
|
|
|
|
|
|
| |
Elimination of interference is not supported on BlackBerry, so
returnGeoValues property will be ignored.
Change-Id: I5c6e3a80ec18f9e0d349d3c4040bfb8067a72291
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
| |
The new qmlimportscanner for static linking depends on the
qmldir reporting the classname of the plugins. So add that
to sensors as well.
Change-Id: I80fd0a1d705ef589268231e6399f612a74b70828
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
| |
This way, clients that are connected will continue to receive updates
after the sensord has restarted, without the need to restart the
sensor.
Task-number: QTBUG-34050
Change-Id: I4a8fbca189764cf23a1453feae5c1fd9ed6911e7
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-QDoc uses \qmlmodule to determine version
-QDoc ignores versions in \inqmlmodule but it is better to remove the
version to avoid confusion
Task-number: QTBUG-32172
Change-Id: Iccab6b3fe201e8f01ddf130cd985bc0482425bf5
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
|\
| |
| |
| | |
Change-Id: I24286cf6c037f10fbbfb6c7e3c7145ebb38c01ed
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If qml type is registered with qmlRegisterSingletonType(), for example:
qmlRegisterSingletonType <QmlSensorGlobal>(package, major, minor, "QmlSensors", global_object_50);
where:
package = "QtSensors"
major = 5
minor = 0
Then it can be accessed like this:
import QtSensors 5.0 as Sensors
var types = Sensors.QmlSensors.sensorTypes();
Task-number: QTBUG-33558
Change-Id: I228fb51e8a2887c59ac8edba1a944a9b2c6ec05f
Reviewed-by: Topi Reiniƶ <topi.reinio@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I746cbf971b88cdffcfc5d675d27d0dda5bac95ad
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds Android backends for QAmbientTemperatureSensor, QPressureSensor
and QProximitySensor.
Task-number: QTBUG-30531
Change-Id: I8d97f62d007c886fcc8dd701e23f6a35a3cbd748
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All illustrations in the documentation show devices with phone
form factors, i.e. portrait orientation. Some tablets have a native
landscape orientation. It is not clear from the documentation
if the sensor coordinate system should be relative to the portrait
orientation or the native orientation.
This change defines the native orientation as the canonical orientation.
Task-number: QTBUG-32144
Change-Id: I870cb3c9b5aec04f2ed8394a4407b53b888e82c3
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ifed287670b09398ef659b9420c3e513a699a0944
|
| |
| |
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-32754
Change-Id: I9037c20953d67584fdfeb4d0fabdfd73f919f14c
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-32751
Change-Id: I65076fa41d5c6a4e716df96bc5156068c1bd0040
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some Windows Embedded 7 SDKs near is still defined, so we need to
undefine it in those cases.
Task-number: QTBUG-32571
Change-Id: I0d48b9dafa2af31f88f48746bfcf4df9fe824554
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| | |
\qtvariable indicates the QT variable needed in .pro files.
Change-Id: Ib3f6def889dddd7c92d0dc943424124af4aa8b09
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
|\|
| |
| |
| | |
Change-Id: Id44a93ddf8dc778f44e9684842a759d585558ee4
|
| |
| |
| |
| |
| |
| |
| | |
Fixes flakiness.
Change-Id: I6e8beaf5106c4dd1e26c3bf038ba9e394d0f080d
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
| |\
| | |
| | |
| | | |
Change-Id: I08bb0d6a9d4b0dddf76f463c32b3a4efdd632f0d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes the flaky unit test failures. It also adds freefall to
unit test.
Task-number: QTBUG-32108
Change-Id: Ia1ee852b1e57b937fd7368073e259a139da9a697
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
| |\|
| | |
| | |
| | | |
Change-Id: I451682790ba1949c150d4045baf9df0cd467d486
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After the change in qtbase 732dcfe7, only the first
sensorgesture plugin was actually being loaded.
Since the FILE argument of Q_PLUGIN_METADATA is optional,
removing that and the json file fixes the following bugs:
QTBUG-31900
QTBUG-31901
Change-Id: I7c0b67605a8fe680c37639f08926140e137dbe66
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I3072c467f9e1d08d5e2869ebdb272d185e612f97
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ref change: 102bdf3
We need to change the implementation to use polling rather
than callback to achieve full performance together with
fine-grained QTimers.
Change-Id: Ic3bf978633c56175eeca90cad8ed764a0b1c9b0c
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ref change: 102bdf3
We need to change the implementation to use polling rather
than callback to achieve full performance together with
fine-grained QTimers.
Change-Id: I895418996b53432642d37279855167d815261d92
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.qmake.conf
sync.profile
Change-Id: I0eaa022110b99fc5bc7cdf6304b5cda3ad3e8f8c
|
| |\|
| | |
| | |
| | | |
Change-Id: I589d4840a0f0cc16656033ab34fcce10b9a499cd
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
\generatelist is not needed for group pages because QDoc will generate
the list already.
Change-Id: If04b07af292e4c05e4b6f933612027773837a6c3
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change-Id: I27eabe7c8b79e03d814deb541db5e7f0b5449099
Reviewed-by: Aaron McCarthy <mccarthy.aaron@gmail.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
qshakerecognizer.cpp:161:28: error: expression result unused [-Werror,-Wunused-value]
The statement was unused, the last branch of an || that was removed in
fb06538f.
Change-Id: I4badb3e5f4272086d44004b9beaca330f8ed7ab6
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-31388
Change-Id: I7a1a0b692d49961d07ae174cb5c2a614295ec98b
Reviewed-by: Shawn Rutledge <shawn.rutledge@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The group in qtdoc is removed because the new overviews on the landing
page replaced the group.
Change-Id: I2e266d8d41ff933c033711880d088fed8f0a8abd
Reviewed-by: Geir Vattekar <geir.vattekar@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
We call it sensord-qt5 now. Use this instead of the qt4 sensord
Change-Id: I54f9de52e572f0afbfef742cf0c84fc64f1469f0
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|