Hi David, What are your thoughts on Craig's points below (from a while ago)? I didn't see any response at the time.
> > Looking again at the APIs you had sketched out and I had sketched in reply, I > think the data types need to be modified for what I am now referring to as > metresHorizontal and also for my metresVertical. Given that altitude is a > double, and distance is a qreal, it seems something like this would be a > better: > > QGeoCoordinate QGeoCoordinate:: appropriateDistanceFunctionName (qreal > metresHorizontal, qreal heading, double metresVertical) > > Note in the attached RFP that an indoor resolution of 1cm is specified for a > device that can measure the distance a user moves. > > Perhaps adjusting altitude with an offset should be done in a separate > function call. > > Also, while metresNorth and metresEast would work okay for small distances, > they probably don't make that much sense for large distances (I think you > would get different resulting co-ordinates if you applied them in the two > different orders). Thanks, - Jeffery MacEachern _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
