* James Turner -- 8/20/2008 1:44 PM: > But, doing this, I wondered - there's these displaced threshold and > stopway values in Robin's data, which we are parsing, storing in > memory, and which are never used by any C++ code - they do get passed > to Nasal, but I'd bet some money no one on that sides uses them either.
I just made all internal runway data available in the Nasal query function, without considering any possible use case. So far I only used those elements that I needed for finding the touchdown point ($FG_ROOT/Nasal/glide_slope_tunnel.nas). Generally, the more information is available, the better. One never knows what clever stuff people come up with, given even obscure data. But then again, we certainly don't need any of the runway details from an airport that's thousands of kilometers away. I'd be fine with having some pieces of information in a file that's automatically(?) loaded with the tile, and can additionally get loaded via Nasal IO on demand, even for very distant airports. m. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
