When using the template, the following should be done for the OPENFILENAME structure:<\/p>\n
- \n
- if the template is a resource in an application or DLL library, then:\n
- \n
- Flags<\/strong> should contain OFN_ENABLETEMPLATE<\/li>\n
- hInstance<\/strong> must point to the module containing the resource<\/li>\n
- lpTemplateName<\/strong> should contain the template name<\/li>\n<\/ul>\n<\/li>\n
- if the template is already in memory then\n
- \n
- Flags<\/strong> should contain OFN_ENABLETEMPLATEHANDLE<\/li>\n
- hInstance<\/strong> member must identify the memory object that contains the template<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
The following code shows how to display a customized file dialog with a template with the ID set to “DIALOG_PREVIEW”:<\/p>\n
\r\n\tCFileDialog fileDialog(TRUE, NULL, NULL, OFN_HIDEREADONLY, _T(\"All files (*.*)|*.*||\"));\r\n\r\n\tfileDialog.m_ofn.Flags |= OFN_ENABLETEMPLATE;\r\n\tfileDialog.m_ofn.hInstance = AfxGetInstanceHandle();\r\n\tfileDialog.m_ofn.lpTemplateName = _T(\"DIALOG_PREVIEW\");\r\n\r\n\tfileDialog.DoModal();\r\n<\/pre>\n
The common file dialog is expanded on the sides so that the new controls have enough space. There are several rules that apply to this repositioning. I will explain them and exemplify with some images.<\/p>\n
- \n
- By default all the controls from the custom dialog are placed below the controls from the original file dialog. The following images show a simple dialog template with a check box and a static control (for a preview). By default, these controls are placed at the bottom of the dialog.
\n![\"Simple](\"\/blog\/wp-content\/uploads\/2009\/08\/custompreviewtemplate1.png\" "\\"Simple")
Simple dialog template<\/figcaption><\/figure>
\n![\"Custom](\"\/blog\/wp-content\/uploads\/2009\/08\/customfiledialog1.png\" "\\"Custom")
Custom dialog with preview controls placed at the bottom<\/figcaption><\/figure>\n<\/li>\n - If the dialog template contains a static control with the id stc32 (defined in DLG.h), the controls will be positioned relative to this control (with the original dialog being displayed in its placed, in the original size).\n
- \n
- all controls above and to the left of stc32 are positioned above and to the left of the original controls, with the same amount.
\n![\"Template](\"\/blog\/wp-content\/uploads\/2009\/08\/custompreviewtemplate2.png\" "\\"Template")
Template with stc32 control position on the right and middle<\/figcaption><\/figure>
\n![\"Custom](\"\/blog\/wp-content\/uploads\/2009\/08\/customfiledialog2.png\" "\\"Custom")
Custom File Fialog with Preview controls on the top left<\/figcaption><\/figure>\n<\/li>\n - all controls below and to the right of stc32 are positioned below and to the right of the original controls.
\n![\"Template](\"\/blog\/wp-content\/uploads\/2009\/08\/custompreviewtemplate3.png\" "\\"Template")
Template with stc32 control position on the left and middle<\/figcaption><\/figure>
\n![\"Custom](\"\/blog\/wp-content\/uploads\/2009\/08\/customfiledialog3.png\" "\\"Custom")
Custom File Fialog with Preview controls on the top and on the right<\/figcaption><\/figure>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n Base on that, if you want to place the preview controls on the right (as I would do), you’d have to place the stc32 control on the left of all the controls from your template. In other words, the template needs to look like this:
\n![\"Template](\"\/blog\/wp-content\/uploads\/2009\/08\/custompreviewtemplate4.png\" "\\"Template")
Template with stc32 on the left of all controls<\/figcaption><\/figure><\/p>\n The resulting file dialog would look like this:
\n![\"Custom](\"\/blog\/wp-content\/uploads\/2009\/08\/customfiledialog4.png\" "\\"Custom")
Custom File Dialog with Preview Controls on the right side<\/figcaption><\/figure><\/p>\n Note: In the above images the stc32 control had the border style set one one hand to make the control visible on the dialog template and on the other hand to have the the original file dialog controls more visible within the resulting file dialog. You wouldn’t do that with an actual file dialog.<\/p>\n
As you could see from the sample code above, it’s very simple to extend the common file dialog. Of course, the part I haven’t shown so far is how to make use of these additional controls. But that is very simple. You just derive CFileDialog, add handlers for the new controls, implement all the logic you want, and instead of instantiating a CFileDialog object you instantiate an object of your derived class. In a following post I will explain how you can add preview functionality to such a custom file dialog.<\/p>\n
You can read more about this topic in the following articles:<\/p>\n
- \n
- Open and Save As Dialog Boxes<\/a><\/li>\n
- How to Show a Custom Common Dialog using CFileDialog<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
Sometimes you want to customize a file dialog, maybe to provide a preview for images or files in general. Fortunately, the common file dialog can be easily extended to achieve this. I will explain in this post how to do that. There are several things one needs to do to extend the file dialog. First … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[7,12],"tags":[451,154,453,156,155],"class_list":["post-349","post","type-post","status-publish","format-standard","hentry","category-c","category-mfc","tag-c","tag-file-dialog","tag-mfc","tag-preview","tag-stc32"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
- How to Show a Custom Common Dialog using CFileDialog<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
- all controls below and to the right of stc32 are positioned below and to the right of the original controls.
- If the dialog template contains a static control with the id stc32 (defined in DLG.h), the controls will be positioned relative to this control (with the original dialog being displayed in its placed, in the original size).\n
- hInstance<\/strong> member must identify the memory object that contains the template<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- hInstance<\/strong> must point to the module containing the resource<\/li>\n
- Flags<\/strong> should contain OFN_ENABLETEMPLATE<\/li>\n