From: Graham <gr...@4o...> - 2007-02-15 20:17:05
|
Hi, back again, I just updated to your latest small changes which solved something which was confusing me - I have being trying my nested folders, which was working fine except for tile maps, which were ignored. I thought it was my problem, but it was that the code I was using expected "TILE" in the file and I had "TILED" copied from your map page. sorted now and it all seems to work well to me. I have got over my problem with gpsd but something which annoys me slightly (not qpegps problem) is that it automatically switches to SIRF binary mode, and doesn't switch back at the end. I have some other software I use occasionally, which doesn't used gpsd and appears to expect NMEA only. However that is a question for the gpsd developers. ztep wrote: > >> 1. gpsd is still started with -s and -p options - latest gpsd should only >> need the device without a switch - "gpsd /dev/ttyS3" >> > > In fact, it should be: gpsd -f /dev/ttyS3 > In fact, no, the manual states that "-f is deprecated and may be removed in a future version. Each command-line argument will be treated as a device to be probed for the presence of a GPS" so the command line only needs the app name and the device. > >> 2. The default script needs to concatenate the lines related to the "stty" >> call, otherwise the current terminal is affected, not /dev/ttyS3 which is >> what is intended. >> > > I have removed this part because as long as I read gpsd now test and > configure the correct port speed. > Good point, and makes things much more simple now. Is there any reason why the stop script isn't called when the Client is destroyed? It looks like this will only happen when the application is quit. The script is there, it is a shame not to use it! I'll do a little more testing now I have it working properly and then upload my alterations for nested map folders in a little while. Graham |