seg fault

Dear Hackers:

Thank you for wxPython! It is a wonderful tool.

We have a problem in which there is a class named "searchPanel" which is
a subclass of "wxPanel". The panel gets destroyed (closed), and then
subsequently one of the methods of searchPanel gets invoked. This
causes a seg fault.

It would be really nice if this situation would cause an exception to be
raised (wxPyDeadObjectError?) so that we could handle this case.

Failing that, we'll have to write another wrapper object around the
searchPanel object that checks if it has been closed before passing the
method call on to it.

So is this behavior (the seg fault in this case) a bug or intentional?

If it's a bug, we'll wait for you to fix it. If it's going to stay,
then we'll start thinking of a workaround.

Regards,

Zooko

http://mnet.sf.net/

Zooko wrote:

Dear Hackers:

Thank you for wxPython! It is a wonderful tool.

We have a problem in which there is a class named "searchPanel" which is a subclass of "wxPanel". The panel gets destroyed (closed), and then subsequently one of the methods of searchPanel gets invoked. This causes a seg fault.

It would be really nice if this situation would cause an exception to be raised (wxPyDeadObjectError?) so that we could handle this case.

Yes, that is what is supposed to happen already. What version platform do you use? Can you reduce it to a small sample program?

ยทยทยท

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