brucedickey@micron.com wrote:
Hi,
I have a MDIFrame app. It prints a few lines to the console window.
The console window does not close when Destroy() is called, but the
app window does close. Don't know if this is pertinent, but the app is
both a CORBA client and a CORBA server. Any ideas how to get the
console window to close?XP sp1, Python 2.2.1, wxPython 2.4.1.2
When you say console do you mean the Windows command line window, or the
wxPython stdout/stderr window that pops up when the print statement
happens?
If the former then you just need to ensure that your app is run with
pythonw.exe (either explicitly or implicitly by changing the file
extension to .pyw.)
If the latter then you can probably fix it by telling the app to use
your main frame as the parent of the popup window when it creates it.
The way to do that is to call app.SetTopWindow(theFrame).
···
-----Original Message-----
From: Robin Dunn [mailto:robin@alldunn.com]
Sent: Wednesday, November 26, 2003 11:20 AM
To: wxPython-users@lists.wxwindows.org
Subject: Re: [wxPython-users] How to ensure console window closes?
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org
Thanks, Robin.
It was the later. But tracked it down to calling an exit function that
calls Destroy() directly from the CORBA interface. Bad, Bad. Now
using CallAfter() and life is happy.
Bruce