Hi James, I'm sure this is not a problem with the gps code but only with the zkv500 code, because it manages itself the route (it has its own route manager), so the gps code just can't use "leg" as it doesn't know the entry point of the leg.
I'm working on it, transferring the route management to the gps code. I hope to get a full working zkv500 gps in the next week. I've got an suggestion for the gps code: a command "nearest-coord" (or better name) which would give nearest navaid for arbitrary coordinates, given by scratch/longitude-deg and scratch/latitude-deg. It will allow to implement a simple navaid-to-navaid flight-plan in a FG session. I tried already months ago, but I can't get it to work properly. best regards seb ps: thanks to Alexis to have committed this patch. James Turner a écrit : > On 8 Dec 2009, at 20:18, Alexis Bory wrote: > >> - Sebastien Marque: Turnpoint is managed using "OBS mode", the route is >> still managed by zkv500's Nasal, only "obs" mode is available >> (seehttp://wiki.flightgear.org/index.php/GPS_internals). It should be "leg >> mode" but I can't get it to work as I expect to. > > Sebastien: You could try asking me, instead of working around problems that I > can (and will!) fix. > > James > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
