On 02/03/2012 10:31 PM, Paul McNett wrote: > O > Have you tested this on Linux and Windows and confirm both lack of drift and > no > missed calls? > > Note that one feature of callAfterInterval() is to keep multiple calls from > occuring. > So if callAfterInterval() is called again for the same function and args > before the > first interval has fired, the original is discarded and now we wait for the > current-call's interval. > Yes, that's why I'm firing the missed calls all at once manually before the next callAfterInterval.
I don't know how I feel about the patch. I has to compute the time since the timer started every time, and it keeps an integer counter of times fired that will eventually get *very large*. The later just plainly raises my red flags. I don't think it'd want it inside the dabo core, but it shows that if someone wants that specific behavior it's easy to subclass/override your dTimer implementation to get it. Nick _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
