CXTPBrowseEdit asserts in your sample

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

Your sample project "BrowseEdit_vc90" asserts when using my own CFileDialog. In your CBrowseEditDlg.cpp there is a #if 0 block where you give code to implement a CFileDialog. I switched that to #if 1 to enable it, then re-built the sample app and ran it. When I click the [...] button to open the CFileDialog it works the first time. I close the file dialog and click [...] again and it asserts at line 377 of dlgfile.cpp. The assert is here:				hr = (
static_cast<IFileDialog*>(m_pIFileDialog))->SetFileTypes(nFilterCount, pFilter);

				ENSURE(SUCCEEDED(hr));
The debugger shows nFilterCount = 2 and pFilter is the expected filter string.

Then I tried what you recommend, to make the CFileDialog a class variable and create it in the dialog constructor. I get exactly the same ASSERT.
Michael

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MichaelN Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 19 September 2006 Status: Offline Points: 112	Post Options Post Reply Quote MichaelN Report Post Thanks(0) Quote Reply Topic: CXTPBrowseEdit asserts in your sample Posted: 27 November 2012 at 4:49pm
	Your sample project "BrowseEdit_vc90" asserts when using my own CFileDialog. In your CBrowseEditDlg.cpp there is a #if 0 block where you give code to implement a CFileDialog. I switched that to #if 1 to enable it, then re-built the sample app and ran it. When I click the [...] button to open the CFileDialog it works the first time. I close the file dialog and click [...] again and it asserts at line 377 of dlgfile.cpp. The assert is here: hr = ( static_cast<IFileDialog*>(m_pIFileDialog))->SetFileTypes(nFilterCount, pFilter); ENSURE(SUCCEEDED(hr)); The debugger shows nFilterCount = 2 and pFilter is the expected filter string. Then I tried what you recommend, to make the CFileDialog a class variable and create it in the dialog constructor. I get exactly the same ASSERT. Michael