Jason Tackaberry wrote: > On Wed, 2006-04-19 at 11:03 +0200, Dirk Meyer wrote: >> I already talked with crunchy about that two days ago, the latest >> version in svn://svn.bitkipper.net/pyNotifier/trunk (that is not the >> one freevo uses right now) can handle our 'idle' signal. > > Ahh, great. Yeah, it's quite trivial to implement. I was just > wondering if there was a reason why it wasn't, or if it was just an > oversight (like crunchy didn't know about gtk_idle_add())
gtk_idle_add is something different. BTW, we should also rename our idle signal to maybe step. kaa.signals['idle']: call every step. gtk_idle_add: call when we have nothing to do So let's say we have a 10ms timer. It will be called 100 times a second. With kaa the signal will also be called 100 times. In GTK it will be called when we have nothing to do, so in most cases more than 100 times. At the other hand, let us say we have a 0 sec timer. So the timer is called again and again as often as possible. And in each step kaa.signals['idle'] is also called. But for gtk it will never be called because the system is busy and not idle. Dischi -- "A deadline has a wonderful way of focusing the mind." - Professor Moriarty, Ship in a Bottle, Star Trek: The Next Generation
pgpgyckEVdgcD.pgp
Description: PGP signature
