Lines Matching full:timers
104 // We would *like* to provide high resolution timers. Windows timers using
107 // is not running our MessageLoop; the only way to have our timers fire in
110 // To provide sub-10ms timers, we process timers directly from our run loop.
111 // For the common case, timers will be processed there as the run loop does
113 // events fire. This mops up the case of timers not being able to work in
115 // pending timers, because they could have already been processed by the
119 // soonest. As new timers are created and destroyed, we update SetTimer.
131 // timers (in case we are running within a nested, external sub-pump).
249 // manager to fire the next set of timers.
251 if (delay < 0) // Negative value means no timers waiting.
482 // the next set of timers.
489 if (timeout < 0) // Negative value means no timers waiting.