on 20/6/05 7:01 pm, Alex Tweedly wrote : I hadn't realized that you could use "0" - I figured "1" was the smallest value that would actually wait, anything smaller would not require a wait.
**************************** Hi Alex I don't understand the point of "wait 0..." When I comment out the line, the program runs 300 revolutions in 2300 millisecs on my system (this is an average of 10 trials, using the default settings as in the stack you uploaded). With the line back in at "wait 0", it takes 1962 ms on average. This seems a little odd. But the weird thing is that the second, faster version with "wait 0..." actually runs far more slowly - the millisecs are lying to me! Using a stopwatch (I know :-)) I reckon it takes about 10 times as long as it reports - around 19 seconds in real time, while the commented-out version is running in just about the time that the millisecs report. I have looked hard at the code, and at the documentation of "wait". Now my brain hurts. What am I missing? regards John -- _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
