C / C++ / MFC

10-Aug-08 20:28

Dear All,

I have created a project (dialog based MFC) to display values in the .dat file. I have 4 dialogs and each of the one dialog should display appropriate values parsed from the .dat file. All the parsing methods have been done in a separate class (which is not a dialog).

I call the parsing method (separate class) from first dialog and when I open the second dialog (by a button click event from the first dialog) the values are displaying correctly. After that, if I go back to the first dialog (by a button click event from the second dialog) all the values seems to be disappeared. I am doing something wrong with my code, please help me.

//First dialog

void FirstDlg::OnBnClickedButton1()//processing the .dat file
{
initvalues();//belongs to another class
bool x=process_file();//belongs to another class which is public
if(x)
{
MessageBox(L"Processing file succeeded");
}
else
{
MessageBox(L"Processing file failed");
}
}

void FirstDlg::OnBnClickedButton2()
{
OnCancel();
SecondDlg ptr1;
ptr1.DoModal();	
DisplayValues();
}
//Second dialog
void SecondDlg::OnBnClickedButton1()
{
OnCancel();
FirstDlg ptr1;
ptr1.DoModal();	
DisplayValues();
}

modified on Tuesday, August 12, 2008 3:14 AM

_AnsHUMAN_ 10-Aug-08 20:42

_AnsHUMAN_

10-Aug-08 20:42

it appears that you are not setting the values to be displayed on the first dialog when you do navigate from the second dialog
BTW are you using a property sheet?

Somethings seem HARD to do, until we know how to do them.
Wink | ;-)

_AnShUmAn_

bhanu_850910-Aug-08 20:53

10-Aug-08 20:53

I also tried to set the values before displaying the result is the same. Please advice. (I used displayvalues(); before calling the dialog.

_AnShUmAn_ wrote:
BTW are you using a property sheet?

I cant understand correctly.

_AnsHUMAN_ 10-Aug-08 21:39

_AnsHUMAN_

10-Aug-08 21:39

bhanu_8509 wrote:
I cant understand correctly.

if you are using a property sheet you can use the sheet class to store the common information. [it's like a wizard then]
Objects of class CPropertySheet represent property sheets, otherwise known as tab dialog boxes. A property sheet consists of a CPropertySheet object and one or more CPropertyPage objects [As you have screens while installing some software where you do have to click on next/back/finish buttons with some view of the dialogs changing]

Somethings seem HARD to do, until we know how to do them.
Wink | ;-)

_AnShUmAn_

David Crow11-Aug-08 3:57

11-Aug-08 3:57

You have two FirstDlg::OnBnClickedButton1() methods. Why?

bhanu_8509 wrote:
After that, if I go back to the first dialog (by a button click event from the second dialog) all the values seems to be disappeared.

Which would be correct based on what you've shown in SecondDlg::OnBnClickedButton1(). The call to DisplayValues() does not happen until after DoModal() has returned.

"Love people and use things, not love things and use people." - Unknown

"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

bhanu_850911-Aug-08 21:18

11-Aug-08 21:18

DavidCrow wrote:
You have two FirstDlg::OnBnClickedButton1() methods. Why?

I am very sorry David. I have done a typing mistake. I am very sorry. Now I have edited my post.

DavidCrow wrote:
Which would be correct based on what you've shown in SecondDlg::OnBnClickedButton1(). The call to DisplayValues() does not happen until after DoModal() has returned.

I understand now that call effect to DisplayValues() will happen after DoModal() has returned. Please tell me how to avoid this. I used Singleton objects using Static members but the same problem presists. Please help me.

Thank you very much for your kind reply.

David Crow12-Aug-08 3:20

12-Aug-08 3:20

bhanu_8509 wrote:
Please help me.

-- Dialog1 <---
|             |
|             |
|             |
|             |
---> Dialog2 --

Having a design such as this is, IMO, a recipe for failure. Why not use a property sheet or tabbed dialog instead?

"Love people and use things, not love things and use people." - Unknown

"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

bhanu_850913-Aug-08 3:16

13-Aug-08 3:16

Sorry David. I cannot understand exactly from your diagram. I am very new to MFC. My requirement is to use Dialogs only, Tabbed dialog and Property sheet should not be used.

Please help me.

David Crow13-Aug-08 3:36

13-Aug-08 3:36

bhanu_8509 wrote:
I cannot understand exactly from your diagram.

I was just implying that having dialog1 call dialog2 which calls dialog1 etc is a bad design. I'm not saying it can't be done, but the solution will be neither straight forward nor elegant.

bhanu_8509 wrote:
My requirement is to use Dialogs only, Tabbed dialog and Property sheet should not be used.

Since a tabbed dialog and a property sheet are both dialogs, your requirement makes no sense.

"Love people and use things, not love things and use people." - Unknown

"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

bhanu_850915-Aug-08 21:49

15-Aug-08 21:49

Dear David,

Please help me how to proceed with good design for my requirement.

Many thanks in advance.

David Crow16-Aug-08 11:36