34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
From: r.hooft at euromail.net (Rob Hooft)
|
|
Date: Fri, 16 Apr 1999 12:30:12 GMT
|
|
Subject: Pmw: Fooling around with the busy window stack.
|
|
Message-ID: <14103.11604.912185.852847@octopus.chem.uu.nl>
|
|
X-UID: 1427
|
|
|
|
I've been trying to fool around a bit with the Pmw busy window stack,
|
|
but I can't manage without some help....
|
|
|
|
I have an application of which the main window is a PmwDialog. In the
|
|
dialog window there are a number of variables that can be edited by
|
|
the user. All user changes are sent in command form over a pipe to a
|
|
subprocess (using subproc.py), which is controlled by a CLI. The
|
|
output of the CLI is shown in a different Toplevel window in a
|
|
PmwScrolledText widget.
|
|
|
|
My question to you: How can I avoid the ScrolledText widget from being
|
|
blocked by the blt_busy system during the active phase of the PmwDialog?
|
|
Is there a way to selectively release the lock on a specified Toplevel?
|
|
|
|
Regards,
|
|
|
|
Rob Hooft.
|
|
|
|
--
|
|
===== R.Hooft at EuroMail.net http://www.xs4all.nl/~hooft/rob/ =====
|
|
===== R&D, Nonius BV, Delft http://www.nonius.nl/ =====
|
|
===== PGPid 0xFA19277D ========================== Use Linux! =========
|
|
|
|
|
|
|
|
|
|
|