Re: How do I terminate CWinApp application?
Just a side note, CFrameWnd deletes itself in the closing process, and if
you returned TRUE in InitInstance, the message pump in the main thread will
stop once it found your main window is gone.
Don't call ExitProcess in an MFC application, because MFC/CRT need to clean
up before they exit. If you want to clean up in your thread and release
resources other than memory (the OS will reclaim the memory after the
process is terminated), exit your worker thread before CFrameWnd is closed.
I usually signal my threads and wait them to complete in the WM_DESTROY
handler of my main window. You can communicate between your main thread and
worker thread using manual reset events (CEvent in MFC, see
http://www.microsoft.com/msj/0797/multithreading.aspx).
--
Sheng Jiang
Microsoft MVP in VC++
"AliR (VC++ MVP)" <AliR@online.nospam> wrote in message
news:SmKri.30206$2v1.3123@newssvr14.news.prodigy.net...
If you use SendMessage then you will close the application and then return
to a none existant code, which will most likely break things (cause fatal
exceptions and such).
You will have to use PostMessage so that things get cleaned up correctly.
The Message will mostly likely get processed right after you return from
your processing function, when the message pump comes back to life.
AliR.
"Alan Williams-Key" <AlanWilliamsKey@discussions.microsoft.com> wrote in
message news:1154A5CE-915C-4706-8167-C560D1022DF3@microsoft.com...
Actually I just tried this. The app closed but I got the "MFC
application
has
encountered a problem and needs to close (blah blah) Please tell
Microsoft
about this problem (blah blah) Debug - Send Error Report - Don't Send."
pop
up. That's OK for me but not my customers.
Alan
"Alan Williams-Key" wrote:
Hey, you guys are quick with the replies, thanks.
I don't think PostMessage (also suggested by AliR) will work for me.
This
happens deep in a data entry process. PostMessage does not have
immediate
effect so I would have to completely rewrite my data processing
functions
to
allow for abnormal exits all over the place.
Would SendMessage work, and which is better, WM_QUIT or WM_CLOSE?
thanks
Alan
"Scott McPhillips [MVP]" wrote:
Alan Williams-Key wrote:
Sorry if this has been dealt with before..
I have a CWinApp application which has to read an validate a lot of
data
from files at start up. In some circumstances it is possible for
the
files to
contain a fata error in the formatting from which my application
cannot
recover. I want to close the applicaiton down cleanly. I have
tried:
AfxGetApp()->CloseAllDocuments(TRUE);
ExitProcess(0);
While this works find in debug configuration, when I try it out on
the
release version it goes very wrong and I get an error message
The instruction at "0x&c809783" referenced memory at "0x003f4544".
The
memory could not be written. Click OK to terminate the program.
I have looked in the disassembly view an there is no valid program
at
"0x&c809783", just question marks.
What is the correct way to abnormally terminate a CWinApp
application?
If you are still in InitInstance return FALSE. Otherwise
AfxGetMainWnd()->PostMessage(WM_CLOSE, 0, 0);
--
Scott McPhillips [MVP VC++]