Re: Unexpected behavior of DoModal()

From:

"Tom Serface" <tserface@msn.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 5 Sep 2006 10:15:54 -0700

Message-ID:

<uwk907Q0GHA.4312@TK2MSFTNGP02.phx.gbl>

I think you should use a modeless dialog instead if you want the parent to
continue functioning.

http://www.codeproject.com/dialog/gettingmodeless.asp

Tom

"Andrey" <Andrey@discussions.microsoft.com> wrote in message
news:7852882E-2586-4FE5-953C-7088DE2CCA32@microsoft.com...

Hello. I've got a new project. Application has been written by other
programmers. The application is MDI-app. App disables its main frame
window
and places it out of screen. It creates Tray Icon. On message from the
Tray
Icon, processed by main frame, descendant of CDialog (CMyDialog) is shown
by
call of DoModal(). To prevent multiple instances of CMyDialog the
DoModal()
method is overridden and it handles multiple instance creation. So the
problem is CMyDialog will not be disabled when other modal dialog is shown
from the thread of CMyDialog. Please note: all modal dialogs is created
with
NULL as pointer to parent window. No thread is created by app at all.
Unfortunately I attempted to reproduce such behavior in clear VS project.
Every modal dialog is blocking the calling thread, even when it is created
with NULL parent. I.e. I suppose it is normal to get blocked calling
window,
and I have something broken in my main project.
If I am thinking right, what else I have to draw my attention to?
You will be welcome with any suggestions. Thank you!