As I said before I am trying to make my app that runs well in Windows
run in *nix and I have come across a strange effect. When I try to
close the app after it has been running for a long time the app gives up
the focus but doesn't die. I put a print statement at the begginnnig of
the close event handler so I am sure that the function is just not
getting called. What could be happening that causes the event to no
longer be associated with the Close function? I thought it might be an
ID problem but I know that no new objects have been created since the
close function works. I am working in Redhat, python 2.2 and wxPython
2.4.0.7.
Any ideas?
Sam
Sam Hendley wrote:
As I said before I am trying to make my app that runs well in Windows
run in *nix and I have come across a strange effect. When I try to
close the app after it has been running for a long time the app gives up
the focus but doesn't die. I put a print statement at the begginnnig of
the close event handler so I am sure that the function is just not
getting called. What could be happening that causes the event to no
longer be associated with the Close function? I thought it might be an
ID problem but I know that no new objects have been created since the
close function works. I am working in Redhat, python 2.2 and wxPython
2.4.0.7.
Any ideas?
Nope. Please try to narrow it down to a small sample app and send it.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
One thing that tripped me up for a while was that Close() doesn't seem to be enough to end the app - you need to Destroy() the top-level frame(s). Could this be factor?
-Matt
Robin Dunn wrote:
···
Sam Hendley wrote:
As I said before I am trying to make my app that runs well in Windows
run in *nix and I have come across a strange effect. When I try to
close the app after it has been running for a long time the app gives up
the focus but doesn't die. I put a print statement at the begginnnig of
the close event handler so I am sure that the function is just not
getting called. What could be happening that causes the event to no
longer be associated with the Close function? I thought it might be an
ID problem but I know that no new objects have been created since the
close function works. I am working in Redhat, python 2.2 and wxPython
2.4.0.7.
Any ideas?
Nope. Please try to narrow it down to a small sample app and send it.
Matt Campbell wrote:
One thing that tripped me up for a while was that Close() doesn't seem to be enough to end the app - you need to Destroy() the top-level frame(s). Could this be factor?
If you catch the EVT_CLOSE event then yes, you do need to call Destroy, because that is what the default event handler does.
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!