"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
The problem is that while it is doing WFSO the message pump is TOTALLY
dead; for example,
no WM_PAINT messages can be handled, no WM_TIMER messages, and it isn't
even possible to
stop the process if it is appropriate to do so.
I prefer to never block the main GUI thread.
joe
On Mon, 18 Jun 2007 15:55:41 -0500, "AliR \(VC++ MVP\)"
<AliR@online.nospam> wrote:
As long as your applications are 32bit. You can use CreateProcess to
start
the new executable and then call WaitForSingleObject to wait until it is
done. That would make the new exe modal to your application.
Here is an example:
http://www.codeguru.com/forum/archive/index.php/t-228971.html
AliR.
<kjell@cablescan.com> wrote in message
news:1181983122.354328.68570@c77g2000hse.googlegroups.com...
Hi,
I have written a MFC application that displays a dialog box. From
this dialog box I would like to open up another dialog box in modal
mode. Usually I would do something like this:
CMyDialog dlg;
Dlg.DoModal();
This works great. But what I would like to do now is to open up a
modal dialog box that runs as a separate process. In order to do this
I have created a new application. This application is a dialog based
application that displays the dialog box. This second application
creates the file ModalDialog.exe. To open this dialog box I do this
instead of the previous code:
ShellExecute(GetSafeHwnd(), "open", "C:\\ ModalDialog.exe", 0, 0,
SW_SHOWNORMAL);
This will display the new dialog box OK but it will not be modal. My
original dialog box that brought up this dialog box will still accept
input from the user.
How can I start a new process containing a dialog box in modal state?
Thanks for your help,
Kjell
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm