Le 15 juil. 06 à 04:29 Matin, Andy Dent a écrit:
On 15/07/2006, at 8:53 AM, Arnaud Nicolet wrote:
When the "window(0).close" method is called, the computer freezes
(well, at least classic freezes)....
Window(0).close
MsgBox "Test"
and I actually get the "Test" message, so the problem is after the
window has successfully closed and no code remains to be executed,
confusing!
Your destructors all remain to be executed, for any members of the
window or static variables.
Try putting breakpoints or system.debuglog messages in all your
destructors and adding destructors to contain these if you don't
have any, so you get to break at the point where member variables
are being destroyed.
Actually, I don't have any destructor at all.
But, just now, I'm seeing a strange thing: I've put a "MsgBox
"Exception..."" in the Unhandled exception event and, while
debugging, I see this msgbox like in a loop. Therefore, I get an
infinite exception. Really strange since I don't have any code in the
close events and the "crash" doesn't occur when I use the close box
to close the window (and quit).
I'll take a look there.
Thanks for your response._______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
