CFileDialog

Environment: C++ VisualStudio 2005 under XP

Type of code: MFC with /crl

The Framework function File | Open works normally and opens the standard FileDialog with the new EXPLORE format.

I have another menu option: File | Load Module that is used to select and load an additional data file. I used CFileDialog for this purpose, but the first time I select this menu option the dialog does not show; the second and following times it works normally.

Article ID 131225 (Nov 15, 2006) describes a similar situation (but in reference to Win95) and the recommended solution consists in disabling the flag OFN_EXPLORE before the call dlg.DoModal().

By doing that in my code, the dialog does indeed show at the first trial, but it is an ugly version of the file dialog. I would be glad to use the EXPLORE format. Can anybody help me on this

Incidentally: the documentation reads that the OPENFILENAME structure is in the member m_ofn of CFileDialog. While this structure is still accessible, actually now it is pointed by m_pOFN. Either one of these members have the same effect, however.

Thanks to all.

Here it is. As you can see, I tried several options. By the way - correction: also the ugly style of File Dialog does not pop up the first time.

void CemDoc:nFileModule()

TCHAR szPathName[_MAX_PATH+1]; // = _T("");

dlg.m_pOFN->lpstrFilter = _T("External Modules\0*.exe;*.E80\0\0\0");

dlg.m_ofn.lpstrTitle = _T("Load External Module");

if(IDOK==dlg.DoModal())

// ...

As you can see, the OFN_ENABLEHOOK is currently disabled in the code I provided to you.

Anyhow:

1. this flag is inserted automatically by the CFileDialog contructor (I read the source code)

2. DoModal asserts if this flag is not used

3. I am not trying to use any special hook - just the default provided by MFC, which works fine with File | Open. My code is in fact almost a replica of the code that the framework uses when it processes OnFileOpen (again, I read the MFC source code)

Thank you Simple Samples, in fact I had already recognized that the KB article was of no use for me.

Unfortunately your clarification does not provide a solution to my problem, though.

Regards

I fixed it!

Incredible as it may seem, the initialization did not like the setting dlg.m_pOFN->lpstrFile = szPathName;

CFileDialog contains an internal buffer m_szFileName (sized _MAX_PATH as required) that it uses to store the selected file, and my attempt to replace it with my own buffer did not work.

However, if instead of an external TCHAR buffer (as was my original code) you use a CString it works fine:

CString strFile;

....

dlg.m_pOFN->lpstrFile = strFile.GetBuffer(_MAX_PATH);

....

is OK.

I cannot offer an explanation for this strange behaviour, nor for the reason why it failed only the first attempt.

Thanks to all.