Melchior FRANZ writes: > Oops ... that was the wrong fix. The new runways.mk4 was there for a reason: > Two string entries were written to and read from the runways.mk4 database > as floats. This was, of course, wrong and potentially harmful, but it was > at least consistent and worked without (noticeable!) problems. > This database bug was fixed yesterday and a new matching runways.mk4 > checked in. That one did obviously not work with the old, broken database > entry definitions. All you had to do was to cvsup and recompile and > runways.mk4 would have worked like before, but without leak. > You have again checked in a broken database that contains strings > declared as floats, which is quite risky. Please create and check in a new > one, created with a CVS-HEAD fgfs. :-P
That doesn't seem to be the case, because the code I was running and the code that generated the database already had your fixes in it (which defined the strings properly as strings.) The current runways.mk4 and code is self consistant (and appears to be correct) and works properly both on my home machines and work machines. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program 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
