You may be better to use a thread for your communication, so your main program thread can keep an eye on the thread, and if it hangs, you could forcefully terminate it, or something like that.
Ross. -----Original Message----- From: delphi-boun...@elists.org [mailto:delphi-boun...@elists.org] On Behalf Of J H Sent: Wednesday, 12 August 2009 6:13 p.m. To: delphi@elists.org Subject: Servicing hanging messages ? I have two applications running sending messages to each other. Currently one of them crashes due to some memory violation, which I am working on. But as it terminates in a non normal way, it does not tell the other app, that it is no longer servicing in-coming messages. Thus the other app. hangs! Is there a way for, say, a third app. or a separate thread to monitor and service such hanging messages ? As it is, I have to start both apps up from scratch. It would be very unlikely the the window handle for the new edition of App 1 is the same. And there is still that hanging message. <P><p><font face="Arial, Helvetica, sans-serif" size="2" style="font-size:13.5px">___________________________________________________ ____________<BR>http://www.sol.dk/ - debat mail horoskoper spil og meget mere</font> _______________________________________________ Delphi mailing list -> Delphi@elists.org http://lists.elists.org/cgi-bin/mailman/listinfo/delphi _______________________________________________ Delphi mailing list -> Delphi@elists.org http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
