Remove unused and unlinked qdocconf file from the project.

Change-Id: I24ba7ae438d4763ca065d88147ff0a023c0ce85c
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Doc: Append handler names to \qmlsignal documentation

Change-Id: I4754a36bd6977cc2bc83a3fee58fb5ce6d2c2c84
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Implement QAccelerometer accelerationMode

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>
Make it obvious what platforms are supported by QtSensors.

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>
Simplify building of simulator based code

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>
BlackBerry: update plugin key

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>
Accelbubble example only really works with a locked UI to portrait

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>
add PLUGIN_CLASS_NAME declarations to plugin projects

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>
Android, Fix generic access to QAccelerometer

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>
Added tizen sensors plugin

Change-Id: Ib455e5c53be47ae4910f56b5b714a4a44e6a8fb3
Reviewed-by: Witold Wysota <wysota@qtcentre.org>
Reviewed-by: Tomasz Olszak <olszak.tomasz@gmail.com>