how to init dialog controls and also use DoModal()

Hi, i like to use dialog templates from the resources, but don't want to add classes for each new dialog.
For example, i have a CListCtrl that is empty. I want it to be filled with data, before it's shown to the user.
The DoModal() creates the dialog itself, and so it doesn't allow me to do any initialization.

So I went to use the callback procedure provided by DialogBox() / CreateDialog(). But this doesn't work. please see code below (1)
Next thing I tried using CDialog::Attach(). But then the DoModal() raises exceptions. please see (2)

Can you experts please give me a tip -

--> I want to avoid creating derived CDialog classes for each resource template each time
AND keep modal behaviour
AND  initialize dialog controls

- Is it possible ? Thanks very much experts!

// callback -------------------------------------------------------------------------------------------
                       // init controls ...
                       return TRUE;
return FALSE;
// attempt 1 -------------------------------------------------------------------------------------------
DialogBox(::GetModuleHandle(NULL), MAKEINTRESOURCE(IDD_MYDIALOG), AfxGetMainWnd()->m_hWnd, (DLGPROC)DlgProc);
// attempt 2 -------------------------------------------------------------------------------------------
HWND hDlg = CreateDialog(::GetModuleHandle(NULL), MAKEINTRESOURCE(IDD_MYDIALOG), AfxGetMainWnd()->m_hWnd, (DLGPROC)DlgProc);
CDialog dlg;
	int retval = dlg.DoModal();

Open in new window

Who is Participating?
alb66Connect With a Mentor Commented:
You can derive a class from CDialog and pass the template to it

class CYourDialog : public CDialog
   CYourDialog( UINT nIDTemplate, CWnd* pParentWnd = NULL );

   virtual BOOL OnInitDialog();

CYourDialog::CYourDialog( UINT nIDTemplate, CWnd* pParentWnd ) <--- pass the template here
   : CDialog( nIDTemplate, pParentWnd  )

BOOL CYourDialog::OnInitDialog()

   // initialize controls here
You must do the controls initialization in OnInitDialog() function.

OnInitDialog is the default handler for WM_INITDIALOG message
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

stev75Author Commented:
Thanks, the question is>
If there's a way to use something like PreTranslate message or a Hook for my dialog instance, that is NOT a CDialog derived object ?
stev75Author Commented:
yes, i thought of a more elegant way, but it may be that it's the only way
stev75Author Commented:
i was way too fast with my previous comment (see below)... in fact, it IS elegant, since it is a good way of constructing the object and very short piece of code ! Thanks !!
AndyAinscowFreelance programmer / ConsultantCommented:
Two points - the first you might have realised, its unclear from your comment.

1)  As alb66 says the OnInitDialog is the place to do initialisation of controls - it is called BEFORE the dialog is displayed so you can fill the controls there.

2) Maybe this class layout is useful.
class CMyBaseDialog : CDialog
class CMyDerivedDialog1 : CMyBaseDialog
class CMyDerivedDialog2 : CMyBaseDialog

Then you can use virtual functions for stuff in the derived classes and have the common code in the CMyBaseDialog class.
stev75Author Commented:
Hi Andy,
2) the "one-level" architecture fits my needs. If you derive another class from your already CDialog -derived class, it would make sense if you want to have  fonts / colours for each dialog, which will be set in the base and each derived will automatically have it.
the point is, when you work with visual studio, and you design you're dialog VISUAL, you will get a new header and cpp file each time, generated by visual studio. I'm going to not use the generated stuff anymore, to have shorter and clearer implementation. This idea came up when I read the comment from alb66. I also think, this will speed up compilation time.
AndyAinscowFreelance programmer / ConsultantCommented:
you can still use the wizard generated files.
Consider - you make a new dialog in resource editor, create a new class for it eg. CMyNewDialog.  Now the wizard generates a cpp and h file with CMyNewDiaog based on CDialog.  In these two (cpp , h) files do a gobal find/replace with CDialog changed to CBaseDialog (or whatever the common class is called).  Finished - you now have the common code linked up.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.