David Megginson writes: > I say yank it completely and either (a) store all of the data in > memory,
This can significantly increase load times ... which is a hassle if you are doing a lot of compile/run testing ... > or (b) split it into directories like the scenery data. The airport > and navaid data that we need are easily small enough to slirp up > into in-memory STL containers -- we have only a little over 16,000 > airports, for example. The downside of this is what if the user requests to teleport to KXYZ? How does the system know which directory to grab the airport location out of? We really need to have at least some info for every airport in memory (or accessible for lookup by name via database.) >From a system design standpoint, I like our current solution, the problem is that it is tripping up some people at compile time. Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
