anygui-users

[Anygui-users] window.destroy() to terminate application.run( ) loop

[Herb J. <hjo...@pl...>]

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". 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.

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. Closing all the
windows opened by the anygui app has no effect. And I'm too new
a Python programmer to use the "try/except SystemExit hack" mentioned
in a previous reply.

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

Also, testbackend.py produces many "hello world" strings and multiple
buttons under Idle, and exhibits the same behavior as described above.It
indicates the current backend is "tk" (tkgui).

Herb Johnson

Re: [Anygui-users] window.destroy() to terminate application.run( ) loop

[Magnus L. H. <ma...@he...>]

Herb Johnson <hjo...@pl...>:
>
> 
> 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

Re: [lists] Re: [Anygui-users] window.destroy() to terminate application.run( ) loop

[David M. <da...@re...>]

On Thu, 2003-04-03 at 00:47, Magnus Lie Hetland wrote:
> Herb Johnson <hjo...@pl...>:
> >
> > 
> > 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.

Might be worth giving IDLEfork a try - http://idlefork.sf.net


> > 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?
-- 
Kind regards
David

--

leave this line intact so your email gets through my junk mail filter