| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I302c83fa8edd1d9e7f350c5d1e2edab3c7c0acf8
|
|
|
|
|
|
| |
Change-Id: I06883e0f2bb16999f13993b69b3701443912c5cc
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
|
|
| |
Since the list of static plugins can contain all kinds of plugins,
failing there is expected.
Change-Id: Ia5051c75691717b2e7279a68ea06f7697cbca053
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
|
|
|
| |
Since this is the default situation.
Change-Id: I9ab76b8ef9402fe39df0aaa532b61bd43b520b71
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
|
|
|
|
| |
Change-Id: I98bd8e3989fc78b552e7685274143c0b8bd90e5e
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|
|
|
|
| |
Change-Id: I46b9a3c20b5169843292057439c80c859ccc7e82
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
|
|
|
|
|
|
| |
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: I04906f381fefa4a60e4a31021d282253a632f833
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|/
|
|
| |
Change-Id: I0ac4e13a17aaff50027c94e06ee1f4f71aa3cdb4
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: I47951d3d277c1d2fc45a7ec36cc01d677ffec7cb
|
| |
| |
| |
| |
| |
| |
| | |
Change-Id: I34160176dec6525e908956959c0749a199e45a2b
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Andrew Inwood <ainwood@blackberry.com>
|
|\|
| |
| |
| | |
Change-Id: I0a9d2e3cbcbe5adcbfc1dbcef3a9d3e7f52d4b90
|
| |
| |
| |
| |
| |
| | |
Change-Id: I7becfab81d56fc45ec7dc76333383503b8abccfe
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ia3f6bdd494b3d167121bd8ee80f81c031a81f45a
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| |
| |
| | |
Invalid sensor data is NaN, and should be ignored.
Change-Id: I6436bdd494b3d167121bd8ee80f81c031e60743e
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |
| |
| |
| |
| | |
Change-Id: I58301f1f05ca0276dbfc6ca0382cb047f036e76c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
|
|/
|
|
|
|
| |
Task-number: QTBUG-38224
Change-Id: I3c7a3d0b3a47696aeb2eee799ae119419ea60713
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
On Android we have to do that via a custom AndroidManifest.
Change-Id: If436bdd494b3d167121bd8ee80f81c031a81f5d5
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Change-Id: I24ba7ae438d4763ca065d88147ff0a023c0ce85c
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: I8d3b0c84091cf7743164c083318e0a115e948d1c
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.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>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ie9b09b93307606f8960df4d212e7a08c1a08c0b5
|
| |
| |
| |
| |
| |
| | |
Change-Id: I09b5df218ad22afefe8a615c80585aa3fb46006f
Reviewed-by: Robin Burchell <robin+qt@viroteck.net>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ic173a32836639e664e8349b28b101ee26a45ff78
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
|\|
| |
| |
| | |
Change-Id: I84535e988c19639c86f8f4837cc8fdb882f3c505
|
| |
| |
| |
| |
| | |
Change-Id: I5639fb872b8e41cc5c5b5968cf1ddf7e247961e2
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| |\
| | |
| | |
| | | |
Change-Id: I61deffeb7b61a4157b9ecb77de35f08d47c4e9bd
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I22dbe4447c14c48bfc812cc8fb5543d5f0fa872f
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.qmake.conf
Change-Id: I849cef727ec7cc88f9dccf5c600cbd59de982e7c
|
| |\|
| | |
| | |
| | | |
Change-Id: I11d540f43baa69f9e857dd793666c1008b217956
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Qt Sensors examples that include additional QML modules fail
to run on Windows, because the application located under a
debug or release subdirectory does not see the module import
path.
This change fixes the issue by adjusting examples' DESTDIR
on Windows builds.
Task-number: QTBUG-33875
Change-Id: Iab8ebc1acd80cf4fe88a7a35b44c42f767da5ccf
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Change-Id: I5082d09607f08c4daad72a8530f7f76feac397fa
Reviewed-by: Matti Paaso <matti.paaso@digia.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
|
|\| |
| | |
| | |
| | | |
Change-Id: Ic6de4c970ff0cb3d5d1b8b6eff4ee020ba485d99
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|