Re: window.destroy() to terminate application.run( ) loop

Magnus Lie Hetland <[email protected]> Wed, 2 Apr 2003 14:47:39 +0200
Newsgroups gmane.comp.python.anygui.general
Message-ID <[email protected]>
Herb Johnson <[email protected]>:
>
> 
> I'm also running anygui 0.1.1 under Win32 (win98), under Python 2.2
> and the 0.8 Idle IDE. WHen running anygui apps under Idle, when
> the app "completes" control does not return to Idle and restores
> the Idle "prompt".

You can't really expect a GUI toolkit to work when run from IDLE,
which uses its own GUI toolkit (Tkinter) -- even if your back-end is
the same (i.e. Tkinter). You'll get two event loops and whatnot.

> Instead text entry is permitted in the Idle
> window, the Idle pull-down menus function. Attempts to exit
> Idle result in no change to that condition. In fact I have to
> use the Close Program window TWICE to terminate the Idle/Python
> task.

Because you have two GUI event loops running.

As far as I can see, this is not Anygui's fault.

> I've read in the tutorial about use of ANYGUI_FORCE_CURSES, but
> setting that variable to a text string (which should be interpreted
> as "true") does not change the behaviour described.

There is no reason to believe that you have support for curses inside
Tkinter.

[snip]
> In short, what is necessary to use anygui in the win32/idle environment,
> as opposed to the DOS command line?

Put it in a file named something.pyw and double-click it?

-- 
Magnus Lie Hetland               "Nothing shocks me. I'm a scientist." 
http://hetland.org                                   -- Indiana Jones


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/