Re: entering a function after dialog is displayed

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 10 Oct 2007 15:32:07 -0700

Message-ID:

<AC51D9DC-F712-49AF-9CA4-41F2DF8646B3@microsoft.com>

I guess that makes sense. I would likely put up a progress dialog in
OnInitDialog() for the initialization or a splash screen, but I can
understand what you are saying. I guess the lengthy initialization is going
to be tedious regardless so there should certainly be some feedback.

Tom

"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:%vbPi.3944$y21.797@newssvr19.news.prodigy.net...

"Tom Serface" <tom.nospam@camaswood.com> wrote in message
news:05513B79-076C-4F0A-B355-B500F1B377B4@microsoft.com...

Another interesting thought. I don't know what, exactly, OP is trying to
do, but I've found precious few things that I couldn't just do in the
OnInitDialog() function to set up the dialog. The window is technically
available to update, it is just not showing yet. After giving this a
little more thought I'm not sure that the PostMessage() idea really is
necessary with MFC even though it does work. What would you do in
another routine that you couldn't just do in OnInitDialog()?

I use this PostMessage() trick to delay lengthy initialization until after
the dialog has appeared.

-- David