Bug: Positioning gives bogus numbers for horizontalAccuracy and verticalAccuracy
Or to be more precise - they are always the same.
Minimal testcase:
import QtPositioning 5.2
PositionSource {
active : true
id: ps
onPositionChanged: {console.log("h/v accuracy:", ps.position.horizontalAccuracy, ps.position.verticalAccuracy)}
}
Just run it with something qmlscene/sailfish-qml. You will get something similar to:
[D] QWaylandEglIntegration::QWaylandEglIntegration:58 - Using Wayland-EGL
h/v accuracy: -1 -1
QMetaMethod::invoke: Unable to handle unregistered datatype 'QGeoPositionInfo'
h/v accuracy: 20 20
h/v accuracy: 20 20
h/v accuracy: 20 20
h/v accuracy: 19 19
h/v accuracy: 21 21
h/v accuracy: 22 22
h/v accuracy: 23 23
h/v accuracy: 23 23
h/v accuracy: 22 22
Great finding! I was suspecting there was a location related bug somewhere. Out of votes for today...
simo ( 2014-01-18 20:54:54 +0200 )edit