oh oh Tom is crossing over into my realem. ;)
A worker thread is a good idea, but if you don't want to go to that
trouble (or if the loop is simple) you can just call a function like:
//
// Release main thread for background processing
//
void GiveTime()
{
// Idle until the screen redraws itself, et. al.
MSG msg;
while (::PeekMessage( &msg, NULL, 0, 0, PM_NOREMOVE ) ) {
if (!AfxGetThread()->PumpMessage( )) {
::PostQuitMessage(0);
break;
}
}
// let MFC do its idle processing
LONG lIdle = 0;
while (AfxGetApp()->OnIdle(lIdle++ ))
;
}
During the loop to give the message process a chance to jump in.
Tom
"Rob" <millerman@ozemail.com.au> wrote in message
news:461dee3e$0$13089$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
Hi,
I've developed a basic dialog program using the MFC foundation wizard.
Upon pushing one of the buttons, a time consuming processing is invoked,
during which the user cannot access the 'Cancel' pushbutton, nor can the
processing in question update any fields in the dialog box. It can
update
the progress bar however.
In order to release the window during this time consuming processing to
allow the user to cancel the processing, do I have to create a separate
thread? Will OnIdol() be a feasible option? Are there any simpler
options that I'm overlooking?
Thanks
Rob