On May 15, 2007, at 20:21 UTC, Mathieu Langlois wrote: > If anyone relied on an OS limitation rather than inputting the > correct value to time their application, I think they deserve to have > their code broken! ;-)
Agreed, though to be fair, it was never really an OS limitation so much as an apparent design decision in the RB framework. 60 Hz is also the resolution of the Ticks function, for example. > My guess is, RS had nothing to do with it, it just happens that > something changed in the OS that made it work faster in RB. Nope. Though it's possible it was an unintended side effect of changing the way the main event loop works, which could be why I never heard about it. (Or, it could be that I just wasn't paying attention -- I confess to not always reading the release notes carefully.) Cheers, - Joe -- Joe Strout -- [EMAIL PROTECTED] Strout Custom Solutions _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
