Hi, uhm ... gpsd is supposed to work with qtmobility on desktop linux?
Till Am Dienstag 05 Oktober 2010 schrieb Hannu Säles: > Hii > > Mobility/location in Maemo uses gpsd...... > gpsd alone works nicely under Qt in maemo.... > > so where is no problem. Use it either way. > > Hannu > > At 20:17 5.10.2010, Till Harbaum / Lists wrote: > >Hi, > > > >Am Dienstag 05 Oktober 2010 schrieb alex.blas...@nokia.com: > > > As David pointed out there are potentially > > multiple sources and the device name is not always standardized. Therefore > > we > >There is no device name involved in talking to > >gpsd. This is exactly what gpsd abstracts. > > > > > didn't feel that hard coding would be > > appropriate. What might work on your desktop may not be a universal truth. > >The use of gpsd is pretty universal. Please tell > >me a single gps aware linux app that doesn't use it. > > > > > Therefore we opted for the middle ground. > > While it is not generalized enough for *all* > > desktops there is a pretty good starting point. > > By the way the QNMEAPositionInfoSource works > > with Windows based NMEA devices too. At this > > point your suggestion does break without further API changes. > >I am pretty sure it does not work with windows > >as windows device names are likely different > >from linux ones. Also your framework includes > >the possibility to provide a defaultsource > >completely transparent to the application. You > >just aren't using this under desktop linux. > > > > > Please keep in mind that Mobility does put > > focus on the Mobile platforms at this stage. > >Yepp ... so i'll wait until it gets a little more mature. No problem. > > > > > While I wouldn't rule out that there is a bug > > in light maps the QNmeaPositionInfoSource is > > tested. In fact, it is the fall back > > > alternative for each example if the platform > > doesn't have a default source. Also looking at > > the code the satellite info source component it > > is clearly optional. Again the NMEA file > > fallback would hit the same code path. Yes, if > > you have a real NMEA source you have to change > > a couple of lines of code to point to your device but that should be it. > >It doesn't even work with the fake nmea source! > >The replay is never started since there's no > >satellite simulation. And a working satellite > >setup is required to start the replay. > > > >Please, just give the current nmea simulation a try. It doesn't work. > > > > > LBNL I would not rule out that your NMEA > > source may have a slightly different NMEA output which may lead to an parse > >As i said: Capturing the very same NMEA output > >to a file and doing a replay from that file works! > > > > > error. You could easily verify this by > > comparing the nmealog.txt with output from your > > device. This would be a bug. LBNL we do not support NMEA 2000. > >This is not the problem. > > > >Regards, > > Till > >_______________________________________________ > >Qt-mobility-feedback mailing list > >Qt-mobility-feedback@trolltech.com > >http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback > > Hannu Säles Oy > Ruomelantie 12 C, FI-02210 Espoo, Finland > http://www.hannusales.fi > tel: +358-400-725374 > _______________________________________________ Qt-mobility-feedback mailing list Qt-mobility-feedback@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
