CFileExportDialog Class

The MFC CFileDialog class only has provision for one default file extension, which is added to a filename if no extension is given. A file export functionality deals with possibly many different file extensions, that have to be added depending on the filetype chosen. The CFileExportDialog class does this. Moreover, when the user selects another filetype from the combobox, the extension in the filename editcontrol is automatically changed.

The usage of the dialog is simple because it mimics the usage of the parent class CFileDialog. Apart from the constructor and destructor, there is only one extra public function, GetFilterIndex(), which returns the index of the selected filetype. This is useful if one extension is shared by two or more filetypes, so the filetype cannot be determined from the resulting filename. In keeping with standard Windows practice, this index starts at 1.
One thing to note is the format of the filter string. This string MUST be of the form "Word File (*.doc)|Text File (*.txt)" .i.e one extension per format, and the formats separated by pipes. Every extension must be put between parentheses and be of the form *.ext.
The initial filetype is determined from the default filename, if it is given. This filename may also be "*.ext". If no default filename is given, the first filetype in the filter string is used.

The CFileExportDialog class is typically used like this:

CFileExportDialog dialog("Save As Type",                          // title
  "Windows Bitmap (*.bmp)|JPEG Compressed Image (*.jpg)|"\        // filter string..
  "Windows Meta File (*.wmf)|Windows Enhanced Meta File (*.emf)", // with file types
  "visualization.jpg");                                           // default filename (may be omitted)

if (dialog.DoModal() == IDOK) {
  CString filename = dialog.GetPathName();
  int filetype = dialog.GetFilterIndex();
  SaveFile(filename, filetype); // defined somewhere in the application
}


Created with MSVC 6, tested under Win95 OSR2.

Download demo project - 20 KB

Download source - 5 KB

Date Last Updated: April 3, 1999



Comments

  • Why different format for filter string?

    Posted by Legacy on 11/17/2003 12:00am

    Originally posted by: _plug

    Why did you make your class use a different format for the filter string than the CFileDialog class? Why not use the same format ("|File Type (*.ext)|*.ext|") and therefore make it compatible with the rest of the worlds code. Also, why not support multiple file extensions per format? When the user selects a format, the first extension would be used.

    Reply
  • How to empty the file name input box initialized filedialog?

    Posted by Legacy on 03/14/2002 12:00am

    Originally posted by: Gempin

    I don't wanna the file name input box has a file name string of the filedialog initialized, that mean there is empty, how to do that? please...
    

    Reply
  • Code Page Error

    Posted by Legacy on 07/27/1999 12:00am

    Originally posted by: Cris Padilla Tagle

    I'm sorry but I could not open your demo program. I am receiving a code page error. It seems to me that the resource needs a Code Page 1252 instead.

    I am thinking if you could send me a copy for English code page.

    Thanks.

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Companies undertaking an IT project need to find the right balance between cost and functionality. It's important to start by determining whether to build a solution from scratch, buy an out-of-the-box solution, or a combination of both. In reality, most projects will require some system tailoring to meet business requirements. Decision-makers must understand how much software development is enough and craft a detailed implementation plan to ensure the project's success. This white paper examines the different …

  • The mobile market is white hot. Building a well-crafted product development plan that addresses market research, strategy, design, and development will provide the greatest chance for success. Each phase of an app's lifecycle is critical to the its overall success and feeds into the next step of the process of product development for the app. This white paper examines the five key phases of mobile app creation, one by one, to understand how they work together to help create a successful mobile app.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date