| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\
| | |
| | |
| | | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A recent change (46959875) in qdoc raised QML types from
subnodes to top-level nodes. This change modifies the
documentation configuration file(s) accordingly.
Change-Id: Iac59992a7ed9bf389502834d0bc694f3e64621b6
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: Martin Smith <martin.smith@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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|\|
| |
| |
| | |
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>
|
|\|
| |
| |
| | |
Change-Id: Icf78a6052ee367ea11638443dd4cf7ecfaf606e3
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|\|
| |
| |
| | |
Change-Id: I3305a1b8bf20b36ad614d1d0492d6a81eb99278a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The behavior of QDebug was fixed in qtbase. Update autotests
accordingly.
Change-Id: Iec8d28f18ca6f5ff1ae960e74d0d978b212ca60b
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|/
|
|
|
|
| |
Change-Id: Icd7c227040671925afa112d353603c16c8e241f4
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Lars Knoll <lars.knoll@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>
|
|
|
|
|
|
| |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following changes are made to the example
- Use of Qt Quick Controls / TableView to present the sensor
information, reducing the example to a single QML file
- Updated launcher main.cpp for the QML example
- Remove separate example doc for the import subproject
- Various fixes to example doc, add a screenshot
- Ensure import module + qmldir are built/deployed to
correct location
Task-number: QTBUG-32881
Task-number: QTBUG-33875
Change-Id: I0ed7c7ebc916fcad6da5e3c66d81be8f348a93e1
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|\|
| |
| |
| | |
Change-Id: Ie5df603a69a8cf2c15f6a6137fcf3edd00d62523
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|