Re: Odd behavior/Hang with CFileDialog in vista.

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 23 Jul 2009 22:22:26 -0700

Message-ID:

<1C8B4D50-DAF7-49F1-AA2A-0886889D9929@microsoft.com>

"James B." <JamesB@discussions.microsoft.com> wrote in message
news:F191C577-06E2-4B20-8D38-82665F1386A1@microsoft.com...

do
{ // Repeat until user either cancels or chooses an existing file
   bResult = false;

   if (openDlg.DoModal() == IDOK)
   { // User has selected a file and pressed OK
outSelectedFile->Assign(openDlg.GetPathName(), NULL); // get the file name
bResult = true;
    }
}
while (bResult && !outSelectedFile->OSIsFileExists());
...
It seems doModal is having issues setting up stuff on vista the second
time
through.

One option I suppose would be to have *Dialog = new CFileDialog (...)
instead of having a local version, and delete and create it each time
through
but this seems heavy handed.

Is it ok/correct to have this kind of a loop and recall DoModal on the
CFileDialog?

I don't know, but I would declare

CFileDialaog openDlg;

in the do loop (rather than using new CFileDialog), so you don't have to
worry about deleting it. See if it works. It's not that big a deal to
reconstruct CFileDialog in the loop.

Better yet, initialize the CFileDialog with OFN_FILEMUSTEXIST and avoid the
loop altogether, since the file dialog will then disable OK button until an
existing file is selected.

-- David