From: aa8vb at vislab.epa.gov (Randall Hopper)
Date: Mon, 19 Apr 1999 14:38:00 GMT
Subject: Tkinter - the app that wouldn't quit
In-Reply-To: <14107.14469.908426.160852@octopus.chem.uu.nl>; from Rob Hooft on Mon, Apr 19, 1999 at 04:07:01PM +0200
References: <19990416144831.A1548022@vislab.epa.gov> <m3pv51xg9g.fsf@devel.no.rwd.dinet> <19990419095013.A62714@vislab.epa.gov> <14107.14469.908426.160852@octopus.chem.uu.nl>
Message-ID: <19990419103800.A63906@vislab.epa.gov>
Content-Length: 1089
X-UID: 1240                                                  

Rob Hooft:
 |>>>>> "RH" == Randall Hopper <aa8vb at vislab.epa.gov> writes:
 |
 | RH> Do I need to add special testing-harness hooks into the dialog
 | RH> class, or is there a general way to determine when a dialog
 | RH> destroys/unmaps itself from outside of the dialog code?
 |
 |Using Tkinter, you can "wait" for a few specific events.
 |
 |"w.wait_window()" will wait for w to be destroyed. But even then, a
 |destroyed window can not be reused!

Ahh, perfect.  Just what I was looking for.

 |I come back to my advertisement: in the *Dialog() classes in the Pmw
 |framework this has all been programmed (using a wait_variable in that
 |case); there is no real reason except "the fun of it" to reinvent this
 |wheel...

Well, there's another reason.  I'm at the getting-up-to-speed stage with
Python and Tkinter, and I want to understand the fundamentals before I go
layering other libraries on top.

But thanks for the pointer.  I'd found Pmw before and do plan to use it in
my next project.  It looks like it can save me a good bit of time for the
off-canvas portions.

Randall




