Hi Alex, thanks for your reply.
Am Sonntag 03 Oktober 2010 schrieb [email protected]: > You need a custom QGeoPositionInfoSource. Since your source seems to be an > NMEA source you might want to give QNmeaPositionInfoSource a try. I am afraid i don't get the concept behind this. If there's one thing i expected qtmobility to do then it's to abstract the hardware layer. Also there's QNmeaPositionInfoSource, but e.g. no QNmeaSatelliteInfoSource which obviously seems to be what the satellitedialog depends upon. The "right" way to use an nmea gps is really to hard code nmea support into the app and to write your own QNmeaSatelliteInfoSource? This would result in a bunch of #ifdefs when using GPS on desktop linux vs. meego/maemo and is exactly what i'd like to avoid. If you e.g. look at the sourcecode of maep/gpxview etc then you'll find exactly this #ifdef'd GPS location switching which i hoped would be gone with qtmobility. Also the maps seem to face the same issue. There are two map demos/examples, one being openstreetmap based and one being nokia maps based. It seems the osm example is handling osm completely in the application and not by qtmobility. Does this make sense? What's the point having a powerful framework when it's up to the application to do the most complex parts itself? Will this change? My expectations were that the map widget reports to the application what map source plagins it has and then uses one of these. What's the point of moving low level map stuff out of the framework into the application? Till _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
