C / C++ / MFC

24-Jan-08 6:47

I have a legacy VC++ 6.0 program that is quite large. Every dialog is user created, even though for many of the dialogs, there was a template created in the resources for the dialog. The problem I am having is that when I call a dialog that allows the user to input an ID number and a PIN to log on to this application, the first time the 'keypad' is displayed, it is displayed in the context of the template that was created, but the second time it is called, the 'keypad' is displayed in the 'user defined' context. Is there a way to get around this problem? It has been baffling me now for months, and granted, I am not a VC++ power user by any means.

Thanks for your assistance.

John P.

David Crow24-Jan-08 7:31

24-Jan-08 7:31

What happens if you remove the template dialog?

"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Reagan Conservative24-Jan-08 8:17

24-Jan-08 8:17

If I remove the template, then I get nothing when I call the keypad class.

The operation of this application is quite large. I'm not sure if you have some idea of what an "Instructor Operating System (IOS)" is to a flight simulator, but it controls every aspect of the flight simulator as far as settings go. In order to use this system, it was decided that it should be user and password protected, so that not just anyone could enter the cockpit and use the simulator. Before I added the password protection modules, the keypad came up as it was designed (being the user design and not just the template). The user design uses some of the template and adds on to it's functionality. It would take paragraphs to fully explain the inner workings of this application, so I'm not sure that you might be able to come up with a viable suggestion as to how to make this work correctly.

I was wondering if it was possible to 'create' the keypad at some other location that's not visible, and then delete it, so that when I call it again, it will not be the first time it has been called and created??

John P.

David Crow24-Jan-08 9:17

24-Jan-08 9:17

Are you using MFC?

Reagan Conservative24-Jan-08 9:19

24-Jan-08 9:19

Yes.

John P.

David Crow24-Jan-08 9:23

24-Jan-08 9:23

Ok, so how are you instantiating and creating the "login" dialog?

Reagan Conservative24-Jan-08 9:47

24-Jan-08 9:47

I create an instantiation of CLogin clog. This creates the login dialog which has text boxes for holding the UserID and PIN values. There are buttons to select the entry for the UserId and PIN and this in turn calls the Keypad dialog. When the user enters the UserID and PIN numbers, they are placed in the text boxes (one at a time).

John P.

David Crow24-Jan-08 9:52

24-Jan-08 9:52

jparken wrote:
I create an instantiation of CLogin clog.

Do you then call Create(), CreateIndirect(), or InitModalIndirect()?

Reagan Conservative24-Jan-08 10:14

24-Jan-08 10:14

I don't call any of these, David. And none of these are called for Keypad as well.

John P.

David Crow24-Jan-08 10:18

24-Jan-08 10:18

I guess I've failed to understand the problem. What is meant by "user design?"

Reagan Conservative24-Jan-08 10:22

24-Jan-08 10:22

I guess that was a poor choice of wording on my part. Almost all the dialogs have been created from a template. So I guess the proper terminology would be "owner drawn".

John P.

David Crow24-Jan-08 10:32

24-Jan-08 10:32

Ok, so what is an "owner drawn" dialog, and how does it differ from a non-owner drawn dialog?

Reagan Conservative24-Jan-08 10:48

24-Jan-08 10:48

In order to explain that, I would have to enter the code for the module that from which just about all the other dialogs are derived. That would be a couple of pages of code that I doubt anyone would want me to paste on the Forum. Here's just a small example of what I'm referring to:

<br />
const UINT CIosDialog::BTN_ID[CIosDialog::NUM_BUTTONS] =<br />
{<br />
   IDC_BN_0,  IDC_BN_1,  IDC_BN_2,  IDC_BN_3,  IDC_BN_4,  <br />
   IDC_BN_5,  IDC_BN_6,  IDC_BN_7,  IDC_BN_8,  IDC_BN_9,  <br />
   IDC_BN_10, IDC_BN_11, IDC_BN_12, IDC_BN_13, IDC_BN_14, <br />
   IDC_BN_15, IDC_BN_16, IDC_BN_17, IDC_BN_18, IDC_BN_19, <br />
   IDC_BN_20, IDC_BN_21, IDC_BN_22, IDC_BN_23, IDC_BN_24, <br />
   IDC_BN_25, IDC_BN_26, IDC_BN_27, IDC_BN_28, IDC_BN_29,<br />
   IDC_BN_30, IDC_BN_31, IDC_BN_32, IDC_BN_33, IDC_BN_34, <br />
   IDC_BN_35, IDC_BN_36, IDC_BN_37, IDC_BN_38, IDC_BN_39,<br />
   IDC_BN_40, IDC_BN_41, IDC_BN_42, IDC_BN_43, IDC_BN_44,  <br />
   IDC_BN_45, IDC_BN_46, IDC_BN_47, IDC_BN_48, IDC_BN_49,  <br />
   IDC_BN_50, IDC_BN_51, IDC_BN_52, IDC_BN_53, IDC_BN_54,  <br />
   IDC_BN_55, IDC_BN_56, IDC_BN_57, IDC_BN_58, IDC_BN_59,  <br />
   IDC_BN_60, IDC_BN_61, IDC_BN_62, IDC_BN_63, IDC_BN_64,  <br />
   IDC_BN_65, IDC_BN_66, IDC_BN_67, IDC_BN_68, IDC_BN_69<br />
};

The same is done for labels, text ids, etc.
Then for example in another file:

CEnvironmentControl::BTN_INFO_STRUCT CEnvironmentControl::btnInfo[] =<br />
{<br />
   //*******************<br />
   // Atmospheric control<br />
   //*******************<br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "B A R O   P R E S S U R E\n-->\n", BaroPressure, CStringType, <br />
    &baroPressureString,NULL,"", 0},<br />
    //&trainerData.baroPresString, NULL, "", 0},<br />
<br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "A I R P O R T   T E M P\n-->\n", AirportTemp, FloatType, <br />
    &trainerData.envInfo.CURRENT_AIRPORT_TEMP, NULL, " \272 C", 0},    <br />
  <br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "S U R F A C E   W I N D S\n-->\n", SurfaceWinds, CStringType, <br />
    &envData.surfaceWindsString, NULL, "", 0},<br />
<br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "A L O F T   W I N D S\n( 8000' MIN ALTITUDE )\n-->\n", AloftWinds, CStringType, <br />
    &envData.aloftWindsString, NULL, "", 0},<br />
<br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "W I N D   G U S T S\n-->\n", WindGusts, FloatType, <br />
    &envData.info.GUSTS, NULL, " kts", 0},<br />
<br />
   {true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
    "T U R B U L E N C E\n-->\n", Turbulence, IntegerType, <br />
    &envData.info.TURBULENCE, NULL, "", 0},<br />
.<br />
.<br />
.<br />
    <br />

Hope this helps explain it a little more. I know it's confusing. I originally, and still do, feel somewhat overwhelmed by this application.

John P.

David Crow24-Jan-08 11:01

24-Jan-08 11:01

So are these controls added to the dialog in OnInitDialog() or some other initialization function? The problem, then, is that they do not show up the first time the dialog is rendered but do show up each time thereafter. Is that correct?

Reagan Conservative24-Jan-08 11:10

24-Jan-08 11:10

Yes, these controls are added in the OnInitDialog(). It is not these other dialogs that have a problem with displaying properly. That only occurs with the Keypad dialog, and the Keypad dialog is not created (derived) from the IosDialog. It is derived from the common CDialog. The class definition is shown below:

/////////////////////////////////////////////////////////////////////////////<br />
// CKeypad dialog<br />
<br />
class CKeypad : public CDialog<br />
{<br />
// Construction<br />
public:<br />
	CKeypad(CWnd* pParent, const WinInfoStruct); <br />
   ~CKeypad();<br />
<br />
 	bool Get_Integer(CString Label, int Min, int Max, int *result=0);<br />
	bool Get_Float(CString Label, float Min, float Max, float *result=0);<br />
	bool Get_Latitude(CString Label,	LAT_DEGREES *result=0);<br />
	bool Get_Longitude(CString Label, LON_DEGREES *result=0);<br />
	bool Get_Angle(CString Label, DEGREES *result=0);<br />
	bool Get_Day(CString Label, int Min, int Max, int *result=0);<br />
	bool Get_Month(CString Label, int Min, int Max, int *result=0);<br />
	bool Get_Time (CString Label, TimeFormats Format, SECONDS Min,<br />
                  SECONDS Max, SECONDS *result=0);<br />
   bool Get_BaroPress (CString Label, float Min, float Max, float *result=0);<br />
// Dialog Data<br />
	//{{AFX_DATA(CKeypad)<br />
	enum { IDD = IDD_KEYPAD };<br />
	//}}AFX_DATA<br />
<br />
private: // Attributes   <br />
<br />
   enum CONSTANTS { NUM_BUTTONS = 14 };<br />
<br />
	WinInfoStruct winInfo;<br />
	CSuperFrame  superFrame;<br />
	CSuperButton m_EntryBtn[NUM_BUTTONS];<br />
	CSuperButton m_Backspace;<br />
	CSuperButton m_Enter;<br />
	CSuperButton m_Cancel;<br />
	CSuperButton m_sbNorth;<br />
	CSuperButton m_sbSouth;<br />
	CSuperButton m_sbEast;<br />
	CSuperButton m_sbWest;<br />
	CEntryBuffer m_EntryBuffer;<br />
	CString m_Title;<br />
	CString m_ErrorBuffer;<br />
   bool settingLat;<br />
   bool m_bShowDirections;<br />
   CRect titleRect;<br />
<br />
   //-----------------------------------------------------------<br />
   // Static Data<br />
   //-----------------------------------------------------------<br />
   const static UINT btnId[NUM_BUTTONS];<br />
   //-----------------------------------------------------------<br />
<br />
private: // Methods<br />
<br />
	void ProcessCharacter(char C);<br />
	void UpdateDisplay(bool New_Title);<br />
<br />
<br />
// Overrides<br />
	// ClassWizard generated virtual function overrides<br />
	//{{AFX_VIRTUAL(CKeypad)<br />
	protected:<br />
	virtual void DoDataExchange(CDataExchange* pDX);    // DDX/DDV support<br />
	//}}AFX_VIRTUAL<br />
<br />
protected:<br />
	// Generated message map functions<br />
	//{{AFX_MSG(CKeypad)<br />
	afx_msg void OnBn1();<br />
	afx_msg void OnBn2();<br />
	afx_msg void OnBn3();<br />
	afx_msg void OnBn4();<br />
	afx_msg void OnBn5();<br />
	afx_msg void OnBn6();<br />
	afx_msg void OnBn7();<br />
	afx_msg void OnBn8();<br />
	afx_msg void OnBn9();<br />
	afx_msg void OnBn0();<br />
	afx_msg void OnBn00();<br />
   afx_msg void OnBn000();<br />
	afx_msg void OnBnDec();<br />
	afx_msg void OnBnNeg();<br />
	afx_msg void OnBnEnter();<br />
	afx_msg void OnBnBs();<br />
	afx_msg void OnBnEast();<br />
	afx_msg void OnBnNorth();<br />
	afx_msg void OnBnSouth();<br />
	afx_msg void OnBnWest();<br />
   virtual BOOL OnInitDialog();<br />
	afx_msg HBRUSH OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor);<br />
	afx_msg void OnPaint();<br />
	virtual void OnCancel();<br />
	//}}AFX_MSG<br />
	DECLARE_MESSAGE_MAP()<br />
};<br />
<br />
//{{AFX_INSERT_LOCATION}}<br />
// Microsoft Developer Studio will insert additional declarations immediately before the previous line.<br />
<br />
#pragma pack(pop)<br />
<br />
#endif // !defined(AFX_KEYPAD_H__A3105D12_254A_11D2_804C_00104B2D1F4C__INCLUDED_)<br />

I use the GetInteger() function to get the UserID and PIN numbers.

John P.

David Crow24-Jan-08 16:05

24-Jan-08 16:05

So what was the previous mention of CLogin for? Is that somehow related to CKeypad?

Reagan Conservative25-Jan-08 3:13