window destroy and re-create problem

Platform: WinXP SP1, Python 2.3.4

Yes, it uses threads. Whenever the user navigates to a new image
(including when a set of images is first displayed), a thread loads into
memory whatever the next image is likely to be. The image-loading
threads are not doing anything to the GUI, I believe. I could certainly
try shutting off that feature.

I tried threats too, but it still exited silently :wink:

Yes, it's totally silent. The DOS command window simply returns to the
next DOS prompt. Running it with pdb also just returns to the DOS prompt.

I'd like to try it under Linux also, but will have to deal with some
SuSE Linux installation difficulties first.

Matthew

···

----- Original Message -----
From: Robin Dunn <robin@alldunn.com>
Date: Thursday, June 8, 2006 5:42 pm
Subject: Re: [wxPython-users] window destroy and re-create problem

Matthew Cahn wrote:

> Is there a way to see all the events that are being processed,
and
> perhaps by which window? That might tell me if the problem
really does
> have to do with sending events to windows that aren't there.

Not built-in. You would essentially have to bind a handler for all
events, for all widgets. PythonCard has a tool that can do this,
it
would be nice to have something similar for use in raw wxPython too.

>
> Is there any other common cause of silent exits?

Not really common, but there are a few. What platform are you on?
Do
you use threads? (Oops, I almost typed that as "threats" :wink: Is
it
really silent (IOW, nothing is printed on the console you started
the
app from?)

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

--------------------------------------------------------------------
-
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-
help@lists.wxwidgets.org