Age | Commit message (Collapse) | Author | Files | Lines |
|
capi-system-sensor will be updated and API will change so until we
update qtsensors to newest API we need to remove the dependency
Change-Id: Id8e793c87da2b19f674965e98aa169d3275c9472
BugTizen: TC-2328
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I7c327cea687cadfc1ac0f71571e3e719ec467f15
Bug-Tizen: TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: If07b2d44d902384026e2cdb2ec7559587f710e89
Bug-Tizen: TC-1008
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I2c381c3f031820e6517e40d8624216b70a4fff96
Bug-Tizen: TC-1008
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: Iad39cd2dd9f9da8ce9ea21366d7f355d16b28621
Bug-Tizen: TC-1008
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I99ae3dd297dd211d9bac66c52d193a769eace8b4
Bug-Tizen: TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I040de883a97dd26b425cb618693d86389989582d
Bug-Tizen: TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I6fdabca4021fe4d8b38f901eb93a9a75774cb516
Bug-Tizen: TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I4f5f461c855c6c74e5cdbafb759d8f3f8875bfdb
Bug-Tizen: TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: Id035395b4bd3d75a5f6aac197167dfe56c1398a5
Bug-Tizen:TIVI-2416
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Bug-Tizen:TIVI-2416
Change-Id: I76cb9a06d3b82fae6b9f0756465632ed4797d371
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Bug-Tizen:TIVI-2416
Change-Id: I2378821d3d58965c2cd645aeb76513e1ce00ae78
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Tizen-Bug: TIVI-2416
Change-Id: I2633eadb4ba2daec7fb9e551c617e9611447fed6
Signed-off-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: Ia601967bb571ba6280971cc702a8b1893a114f1e
|
|
|
|
|
|
Tizen sensors are available for mobile and common profiles.
Change-Id: Icc3c3357e932dac3808aee891e467fcc9dad2181
Reviewed-by: Philippe Coval <rzr@gna.org>
Reviewed-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: Ib455e5c53be47ae4910f56b5b714a4a44e6a8fb3
Reviewed-by: Witold Wysota <wysota@qtcentre.org>
Reviewed-by: Tomasz Olszak <olszak.tomasz@gmail.com>
|
|
Change-Id: I3e34ba8503f7b4675a6c629ff5baf9370a7cf63c
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
Task-number: QTBUG-41250
Change-Id: I788332e3db66e8188fc7d64d1e31995f4b432932
Reviewed-by: Martin Smith <martin.smith@digia.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
|
|
QtSensors was released first by Qt 5.1.
A few whitespace changes go along as well to unify the formatting.
Change-Id: I6f6e15c95c1a5f33731782e429e87cef68e96e3b
Task-number: QTBUG-36775
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
|
|
The example doesn't offer much example value. The accelerometer is
presented by the accelbubble example too but doesn't have all the
Qt3d dependencies. Cutting those dependencies is much cleaner.
Task-number: QTBUG-31076
Change-Id: I074b24974cbd630d7b6ccc9eb21d8cabc96da86c
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
|
|
1.) Remove dependency on QtSystemInfo. The module is not officially
supported at this stage and screen saver related code is not really
required for the example.
2.) Add AndroidManifest.xml to lock the screen orientation in portrait
mode. Since the example depends on the tilt sensor a rotating UI is
messing the game up.
3.) Port app to current TiltSensor API.
The game works but its biggest problem remains the UI. It uses
fixed-size UI elements which makes it tiny on High DPI screens.
Task-number: QTBUG-31076
Change-Id: I73df9361b5171da930df66072e8ee9eba89b71ad
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
Conflicts:
.qmake.conf
Change-Id: Ic6cdc4873d153c8a7d5d233b70c50879eaf49c9c
|
|
Change-Id: I302c83fa8edd1d9e7f350c5d1e2edab3c7c0acf8
|
|
Change-Id: I7c2b192d4b3b4d745096058fd69921d855433f85
|
|
- 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>
|
|
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>
|
|
Conflicts:
src/plugins/sensors/sensorfw/sensorfwproximitysensor.cpp
src/sensors/qcompass.cpp
Change-Id: Idfcbbfe1757a4b827663453abc27f4026cd3d752
|
|
Change-Id: Ic13d2d1e400a92b2f0c3c83e279c58b799f9d06b
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
|
|
The compass behaves like the other sensors: it is
measured relative to the top of the device.
Change-Id: Iddc4ad6a16f8b09d26a9d300155324bb8d378b76
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
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>
|
|
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: I6afcbcf691e203491ee563168c19d084c051a449
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
|
|
-url inherited from the url variable set in qtbase/doc/global
Change-Id: I0bab30bfd8e6f386aa94c2e28d13184fde9af63c
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
|
Conflicts:
.qmake.conf
Change-Id: I01306a5c0d34f85efdbc5f947add4dee0cccbf8e
|
|
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
|
|
Conflicts:
.qmake.conf
Change-Id: Ia804a9a975baea0f971c7bea004c5ce403d1adee
|
|
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>
|
|
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>
|