| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to the docs (CMMotionManager class reference) there are
two ways of interacting with the accelerometer; Either through the
callback API (NSOperationQueue), or peridic sampling (polling).
Our first implementation of IOSAcceleometer used the former
technique, which turns out to have bad performance when using the
sensor together with a fine-grained QTimer. And this case is
pretty common when using sensors together with e.g QML.
Reading through the docs more carefully, they recommend using the
polling technique when creating games instead since the
NSOperationQueue introduces some overhead. So this patch does
that, change the implementation to use QTimer based polling. And
this solves the performance issues found.
Change-Id: Ifde0d2292302467afb8db90a954ef45f3238350e
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The code as it stood made use of an extra obj-c class
to listen for sensor readings. This is not needed with
the block (lambda) API used by CMMotionManager.
This will also make IOSGyroscope and (soon) IOSMagnetometer
follow the same code pattern.
Change-Id: If945f8616f4cdde98b31382fcd9c555c2b490c4a
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@digia.com>
|
|
|
This change implements an accelerometer for iOS.
Change-Id: Id6de98427312bc0be42935fd9704117665d1e4a2
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
