Re: [Tkinter-discuss] Persuading after_idle callback to only get called when the window is mapped

> This sounds like you are trying to access tk from within two different > threads which is generally a bad idea, though it may *seem* to work > sometimes. > Maybe we can provide better help if you could post a short code snippet > that demonstrates your problem. > > Regards > > Michael > Hi Mich

Re: [Tkinter-discuss] Persuading after_idle callback to only get called when the window is mapped

Hi Geoff, On Wed, 13 Jan 2010 20:38:53 +0100 Geoff Bache wrote: (...) > Hi Michael, > > I'm trying to write a basic GUI testing tool (in fact, I'm trying to > add basic Tkinter support to PyUseCase, which has only worked with > PyGTK so far) > > The basic plan when replaying is thus to add an

Re: [Tkinter-discuss] Persuading after_idle callback to only get called when the window is mapped

On Wed, Jan 13, 2010 at 10:35 PM, Geoff Bache wrote: > Hi Geoff, > > On Wed, 13 Jan 2010 20:38:53 +0100 > Geoff Bache wrote: > > (...) >> Hi Michael, >> >> I'm trying to write a basic GUI testing tool (in fact, I'm trying to >> add basic Tkinter support to PyUseCase, which has only worked with >>

Re: [Tkinter-discuss] Persuading after_idle callback to only get called when the window is mapped

Hi Geoff, On Wed, 13 Jan 2010 22:41:55 +0100 Geoff Bache wrote: (...) > > Hi Michael, > > Thanks for your detailed reply. I feel also that there should be a > simpler solution and I can't say I *want* to use threads exactly. What > I think you're missing above is that a GUI testing tool is sup