Re: Problem with MFC Thread

From:

"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 16 Sep 2008 11:44:01 -0400

Message-ID:

<OPZqWMBGJHA.6132@TK2MSFTNGP04.phx.gbl>

Each thread has its own message pump. So the worker thread should not
access the controls in the main thread dialog - If it works at all it blocks
the worker thread until the main thread performs the update. Ali shows how
to update the progress control from the worker thread. And the worker
thread cannot pump messages for the main thread, so get rid of your
ProcessMessage function. Nothing like that is necessary: The main thread
should be permitted to run and process messages automatically at all times.
You have put a WaitForSingleObject call in the main thread - that's wrong.
It you use events to control the worker thread then the WaitForSingleObject
call(s) must be in the worker thread.

"Lucress Carol" <incognito.me@gmx.de> wrote in message
news:6c0c5db3-6262-4f44-9bae-78342b9d68de@e53g2000hsa.googlegroups.com...

Hi everyone,
I've created a MFC Dialog with a Progress Bar Control, a Stop Button
and a Start Buttton.The idea is to start the progress bar Control by
clicking on the Start Button and I would like to pause (Stop Button)
the process at anytime and continue it when I click on the Start
Button again.
I 'm able to stop the process of the Progress Bar but when I try to
continue the process the whole thing crash...
Here is how my code looks like:

xx

--
Scott McPhillips [VC++ MVP]