From: John H. <jd...@gm...> - 2008-07-30 21:38:25
|
On Wed, Jul 30, 2008 at 4:31 PM, Eric Bruning <eri...@gm...> wrote: > I tried with the Tk backend, and I'm seeing the same problem as Eric F > has with GTK. The problem seems to be with idle_event not getting > triggered on some of the backends. > > The checkins having to do with idle_event from the end of June > indicate that idle_event is still somewhat experimental. > > What's the current status of idle_event? Can I help in some way? I was working on idle event, to make a backend neutral api for idle processing, animation, etc... There was a particularly nasty problem with tk since I had to do the threading calls myself and I am no threading guru, so I reverted some of the changes, mainly because of the problem of cross thread signal handling blocked the CTRL-C interrupts. These changes were added in r5652 r5652 | jdh2358 | 2008-06-23 16:39:11 -0500 (Mon, 23 Jun 2008) | 1 line draft idle/timeout api and subsequent refactoring r5653 | jdh2358 | 2008-06-23 23:17:21 -0500 (Mon, 23 Jun 2008) | 1 line replaced idle handler with idle event but then reverted when Nils reported the CTRL-C bug in r5655 | jdh2358 | 2008-06-24 08:56:55 -0500 (Tue, 24 Jun 2008) | 1 line removed idle support from tkagg until I figure out interrupts So the implementation is incomplete and tkagg needs to most work, since for other GUIs it is fairly easy to pass through the native enent handling. I am not sure what the problem is with GTK right now, and haven't had a chance to look at it. JDH |