Month
Month
For this month's meeting we will have a review of the material covered during the last year or so. I will point out some of the more interesting problems and concepts that were demonstrated as well as answer questions. In some cases, we will have discussions and/or debates on possible alternatives.
For the actual meeting we had an interesting discussion based on some questions from one of the members. The problem was to create a DLL file that contained a dialog box. This dialog box was to receive messages from the main calling program and then display them in an edit control. As can be seen in the above picture, the edit box displays the message. Here's the code for the Launcher program:
BOOL CLauDlg::OnInitDialog()
{
CDialog::OnInitDialog();
FunctionOne("Hello Ron number 2");
return TRUE; // return TRUE unless you set the focus to a control
}
class CMsgBox : public CDialog
{
// Construction
public:
CMsgBox(CWnd* pParent = NULL); // standard constructor
// Dialog Data
//{{AFX_DATA(CMsgBox)
enum { IDD = IDD_DIALOG1 };
CEdit m_Edit1;
CString m_EString;
//}}AFX_DATA
...........
}
int FunctionOne(char *arg)
{
CMsgBox xxx;
xxx.m_EString = arg; // See UpdateData(FALSE)
xxx.DoModal();
return 0;
}
FunctionOne() and the class CMsgBox are contained in the DLL which is called Feb03, Most of the discussion centered around the integrated development environment and the class wizard: how to set the parameters for passing this information back and forth from the main executable to the EXE file. It was a very interesting meeting.