Shall we declare Tkinter dead? No-one seems interested in it ;o)

[Mike Fletcher]

Nested mainloops are a Tkinter feature caused by such things as
widget.wait() and managed by such things as widget.quit() .  _I_ never even
use Tkinter, I'm just trying to make it compatible with micro-threads (so
other people can use it), so _I_ would _never_ use a nested mainloop.  I
agree, nested mainloops suggest the need for a different architecture: FxPy
and wxPython spring to mind ;o) .

>From that article looks as though just binding the destroy event should be
sufficient.  Cool.

Success is in the eye of the foreclosing banker,
Mike

-----Original Message-----
From: Cameron Laird [mailto:claird at starbase.neosoft.com]
Sent: Monday, October 30, 2000 10:24 AM
To: mfletch at tpresence.com
Subject: Re: Shall we declare Tkinter dead? No-one seems interested in
it ;o)
...
"... nested mainloops ..."?!!?  Mike, WHAT
are you doing?

I have a strong instinct that nested mainloops
are a hint that there's pervesity afoot, and
that I'd look for a different architecture.  I
know, though, that you're successful at what
you do, so maybe it'll work for you.
>and the WM_DELETE_WINDOW, if I understand correctly, either would indicate
>that the root window is being destroyed.
Sort of.  Readers with further interest in this
topic might want to notice, for example, 
<URL:http://deja.com/=dnc/getdoc.xp?AN=582614369>
...