[pygtk] gobject.timeout_add timeout recalculation

2008-05-15 Thread Mitko Haralanov
In my application, I am using gobject.timeout_add to trigger periodic updates of the status of a number of machines. However, I am having a bit of trouble understanding exactly how the timeout is calculated. According to the documentation: After each call to the timeout function, the

Re: [pygtk] gobject.timeout_add timeout recalculation

2008-05-15 Thread skip
Mitko However, I am having a bit of trouble understanding exactly how Mitko the timeout is calculated. According to the documentation: Mitko After each call to the timeout function, the time of the Mitko next timeout is recalculated based on the current time and

Re: [pygtk] gobject.timeout_add timeout recalculation

2008-05-15 Thread Mitko Haralanov
On Thu, 15 May 2008 18:48:22 -0500 [EMAIL PROTECTED] wrote: I believe it works like this: set wakeup for X milliseconds from now call your callback if it returned true: set wakeup for X milliseconds from now call your callback if it returned true: set

Re: [pygtk] gobject.timeout_add timeout recalculation

2008-05-15 Thread skip
If X is 2500ms and your callback takes 2ms to execute, the interval between successive calls will actually be 2502ms. Mitko Unfortunately, it is how it work. In fact, that how I would like ^ not? Mitko it to work. Here is what my testing shows: