| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
From Qt 5.7 -> LGPL v2.1 isn't an option anymore, see
http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
Updated license headers to use new LGPL header instead of LGPL21 one
(in those files which will be under LGPL v3)
Change-Id: Id129b1497aa9d61fd16332e3b324f28dcf7bdd5b
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
|
|\
| |
| |
| | |
Change-Id: I4286dcb9262bf38960ff3852932012718aaa5d65
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It should be registered/unregistered depending on the availability
of the default light sensor rather than the default accelerometer.
Also mark the ambient light sensor as supported by the generic plugin
in the documentation.
Change-Id: Iff3828140b9549d994563fb736014091e568e867
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
| |\
| | |
| | |
| | | |
Change-Id: Ic4c5a95a53ff695b879314cd2d6092bcbe427d94
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes it possible to use Tilt sensor from generic plugin.
Task-number: QTBUG-47854
Change-Id: I14883e8d4a18a56c52845a4a5172c8c46bfe385f
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ife5ca9224e4a1ac0b57a25aeb59e2f23e505082b
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
iio-sensor-proxy is a daemon that listens to sensors on IIO
subsystem on Linux and provides access to the sensor readings
over D-Bus. Currently it provides only orientation and ambient-
light level.
https://github.com/hadess/iio-sensor-proxy
Change-Id: I035bda0b43a16552a9f2bd88a064e53d5f105451
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
|
|
|
|
| |
[ChangeLog][QtSensors][Platform Specific Changes] Removed support
for BlackBerry 10 from QtSensors.
Change-Id: I56788caaa53797b7d4e23bb053c3ea8b460b1341
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
|
|\
| |
| |
| | |
Change-Id: Icc01abe0bc7368455527b5f4b5299b4cb9f2b177
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-45516
Change-Id: I45215714e8f5e4693e43d022a3ca313576c85d79
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I9031610c02d9418b46339c34b02264a03600403c
Task-number: QTBUG-45691
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
From 5.5.0 -> WinRT port is licensed with LGPLv3, see
http://blog.qt.io/blog/2015/04/29/windows-10-support-in-qt/
Change-Id: I1c78b8f11d1640e36e6b90eea47500c5dd5408ee
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@theqtcompany.com>
|
|\|
| |
| |
| | |
Change-Id: I06a505894844bfd17eb07106bed0c07ca2f9f79c
|
| |
| |
| |
| |
| |
| |
| |
| | |
No need to use a double negative in the chain of data to arrive
at the correct values.
Change-Id: I694037bb7f83083d3d281ec9544d7fa300861f1a
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| |
| |
| |
| |
| | |
Change-Id: Iecb6fe8637001d3005aa04c58d1d888f534c5082
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
|\|
| |
| |
| | |
Change-Id: If6f44fe2cd69bae92cddd4682e952f2528b85184
|
| |
| |
| |
| |
| | |
Change-Id: Ibb4d335ff43a91f84f346ab32847ab376830ed35
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| | |
genericrotationsensor.cpp:85:37: error: 'sqrt' was not declared in this scope
Change-Id: I871b88130debdfd0a64421e4da8a451b586e7ba6
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
|
|\|
| |
| |
| | |
Change-Id: I7b64e129ef941420378cda207f5fdf90efe4c463
|
| |
| |
| |
| |
| | |
Change-Id: I69d15c8af9b6e5acde9d86e185395590369baab6
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
|
| |
| |
| |
| |
| | |
Change-Id: Id1247f797873395c38251ba098bfa848a06f10ee
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
|
|/
|
|
|
|
|
|
|
| |
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: I141862df4ed2475c05ebbeb8fe447c4a6e736849
Reviewed-by: Antti Kokko <antti.kokko@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The dummy sensors plugin will start fake sensors that emit 100 updates
per second. This should not be the default sensor returned when a
user requests a sensor.
These sensors were default on Linux.
Task-number: QTBUG-39475
Change-Id: Ia276e904f93dfeef95f7490ec7cb51cad260a2a8
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
- Renamed LICENSE.LGPL to LICENSE.LGPLv21
- Added LICENSE.LGPLv3 & LICENSE.GPLv2
- Removed LICENSE.GPL
Change-Id: I99c601a398559886c2900f3e04833acfceba8263
Reviewed-by: Antti Kokko <antti.kokko@digia.com>
Reviewed-by: BogDan Vatra <bogdan@kde.org>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@digia.com>
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/plugins/sensors/sensorfw/sensorfwproximitysensor.cpp
src/sensors/qcompass.cpp
Change-Id: Idfcbbfe1757a4b827663453abc27f4026cd3d752
|
| |
| |
| |
| |
| |
| |
| |
| | |
Change I5c1bf3999ad2268c0dba9b3fe511d999c2e63fd9's forward porting from Qt 5.1
removed this, thus the interface was never set, thus sensors all broke.
Change-Id: If3b14b5ebd20e6cb64bc2000b23a2c1e37d36b05
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1)tracing plugin loading
2)m_remoteSensorManager can be nullptr
But it seems it does not solve incorrect initialization in the case
manager interface is nullptr: init() for different sensors does not
check initDone
3)split initSensor() to template function and function
most of initSensor() does not depend on template param, so it is
better to split it -> less code should be generated
4)do not use sensor manager if it is invalid
5)correct class members initialization order
6)assert sensor interface is not null
From what I saw according to logic it should not happen so using
Q_ASSERT for better maintainability
7)check local interface pointer in SensorfwTapSensor::start()
Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>
Change-Id: I5c1bf3999ad2268c0dba9b3fe511d999c2e63fd9
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
This ensures things are setup and work properly.
Change-Id: I23c8b53e760d49695c5ae207eed77a2e7d2be3a4
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ic13d2d1e400a92b2f0c3c83e279c58b799f9d06b
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Several sensors were setting the dataRate without checking the value
first. If the dataRate is zero, then don't set the native rate (use
the default).
Task-number: QTBUG-40664
Change-Id: I50e78fd071bd1f56e47baf23b74900b8a6e6c7eb
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some sensors need to set a dataRate in which they are providing values.
Values are in Hz, hence the conversion and defaults to 1Hz like on other
backends as well.
Task-number: QTBUG-40664
Change-Id: I980155f9b4b2772e8420df4b51e8ebb5cdea6037
Reviewed-by: Andrew Knight <andrew.knight@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
AmbientLight as well as Orientation sensors have been added to the
Windows Phone 8.1 API. Furthermore accuracy for QCompass is now
available on all WinRT related platforms.
[ChangeLog][Windows Phone] Add support for
QAmbientLightSensor and QOrientationSensor with Windows Phone 8.1
Task-number: QTBUG-39627
Change-Id: I6b2674c0d9935b874f35e6453f1e51d811133264
Reviewed-by: Andrew Knight <andrew.knight@digia.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: I01306a5c0d34f85efdbc5f947add4dee0cccbf8e
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case of an unsuccessful call of the GetDefault function the returned
HRESULT does not have the FAILED status but the returned sensor is 0.
Task-number: QTBUG-39698
Change-Id: I42a8327c1d7687ab7a8ca71be5a2234b2c4e0b38
Reviewed-by: Andrew Knight <andrew.knight@digia.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ia804a9a975baea0f971c7bea004c5ce403d1adee
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The QtSensors documentation says that if Gravity mode is not available,
we should silently fall back to the default Combined mode.
In addition, add null pointer checks in case we try to ask for non-existent
sensors in the future.
Task-number: QTBUG-39335
Change-Id: I6c18622d081db4e3a7d07c744bb0b746e3f5c6ff
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I7becfab81d56fc45ec7dc76333383503b8abccfe
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug where the proximity sensor would send the initial
signal only when it was not closed. This will send it regardless.
Change-Id: I5f388e671091ae2a7719f700a049cea41bfaa0db
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ia70486a0c6b813829ffd633f5334945f73d3b628
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|\|
| |
| |
| | |
Change-Id: I07a6842afc72f56c82e82906429fa422f9a82de2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Generic access to QAccelerometer through QSensor was broken by my
previous change: 971fc95eca1d9db93aa4bdb75793dfe83e4a97db
When using a QSensor* to access the accelerometer, the qobject_cast
would fail, and return 0. I fix this by defaulting the accelerationMode
to Combined when a QSensor* is used.
Change-Id: If8389808a416807b72709a13ca315aa23bbf94a0
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|