Curtis L. Olson writes: > Yes, if you use an int and track time in increments of 1 / 1,000,000 > then you get about 30 minutes before you hit an anomaly. This bug > caused problem in the past such as radio station searches to only > happen every other 30 minute period, or panel text to stop updating. > You have to be very careful to think through the amount of possible > time accumulation when doing the math. This is a subtle bug because > when you are developing code, you rarely test for more than a few > seconds at a time. That said, I haven't looked closely to see if any > of these problems are in the latest code ... but it's something to > keep in mind when dealing with time sensitive code.
Since we pass a dt rather than a counter, it shouldn't be a problem. By the way, I modified main.cxx so that dt=0 whenever the clock is frozen -- that way, the instruments don't keep settling (or drifting) during a pause. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
