Re: Revive Tk
- From: Gerhard Reithofer <gerhard.reithofer@xxxxxxxxxxxxxx>
- Date: Wed, 17 Jun 2009 22:59:13 +0200
On Thu, 11 Jun 2009, Georgios Petasis wrote:
O/H Robert Heller ??????:
At Thu, 11 Jun 2009 14:01:12 +0300 Georgios Petasis
<petasis@xxxxxxxxxxxxxxxxx> wrote:
O/H dkf ??????:
On 10 June, 18:36, Don Porter <d...@xxxxxxxx> wrote:You may have problems with some dialogs though :-)
One possible workaround would be to [load] Tk in a slave interp.The other workaround is to withdraw the "." window and only let the
Then when it's made dead in one, you can [load] Tk again in a new
slave interp to get going again.
user close its children. That works pretty well in my experience, and
is something I'd recommend for all complex applications. (It can also
make working with widget pathnames easier in practice...)
Donal.
Not if you are careful to *always* use the -parent option available for
all of the tk_<mumble> functions.
Or wrap the dialogs into other procs, that set -parent to the window that has
....
Back after 2 weeks.
THX to all.
--
Gerhard Reithofer
Tech-EDV Support Forum - http://support.tech-edv.co.at
.
- References:
- Revive Tk
- From: Gerhard Reithofer
- Re: Revive Tk
- From: Jonathan Bromley
- Re: Revive Tk
- From: Don Porter
- Re: Revive Tk
- From: dkf
- Re: Revive Tk
- From: Georgios Petasis
- Re: Revive Tk
- From: Robert Heller
- Re: Revive Tk
- From: Georgios Petasis
- Revive Tk
- Prev by Date: Re: A book on the Oratcl package
- Next by Date: Re: Bug in font handling under windows? [tcl 8.6]
- Previous by thread: Re: Revive Tk
- Next by thread: supress sysout of spawn
- Index(es):
Relevant Pages
|