C / C++ / MFC

14-Aug-07 5:11

VC++ v6

Is there a dirty flag for property pages? In other words what, or how does a property page communicate to its parent that it is dirty(data has changed)?

I have a dialog with four tabs(property pages), and changes to the first tab are recognized by the dialog and it prompts the user with the standard save changes, yes/no/cancel. If a change is made on a tab other than the first, and a subsequent tab is clicked on, the dialog never recognizes the changes and the close button just exits the dialog without prompting the user or saving any of the changes.

jhwurmbach14-Aug-07 5:15

jhwurmbach

14-Aug-07 5:15

Has your Document a dirty flag? And does the first page set it?
All in all, the neither the Sheet nor the Pages should hold the Data: The Document should.
And this is also true for any but the most trivial CDialog-based application. The "document" would have another name here or be part of some other class.

Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
George Orwell, "Keep the Aspidistra Flying", Opening words

littleGreenDude14-Aug-07 5:19

14-Aug-07 5:19

is there a typical way that this is handled? Does the child (property page) send a message to the parent to notify the parent that data has changed?

jhwurmbach14-Aug-07 5:25

jhwurmbach

14-Aug-07 5:25

The CPropertySheet is a CWnd-descendant. It has a GetParent() function.
You *know* what class its parent is and can cast the parent CWnd-pointer appropriately to call function directly.
Message calls would work also.

Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
George Orwell, "Keep the Aspidistra Flying", Opening words

led mike14-Aug-07 5:47

led mike

14-Aug-07 5:47

littleGreenDude wrote:
is there a typical way that this is handled?

See the Model-View-Controller Design Pattern[^]

David Crow14-Aug-07 7:49

14-Aug-07 7:49

littleGreenDude wrote:

Is there a dirty flag for property pages? In other words what, or how does a property page communicate to its parent that it is dirty(data has changed)?

If you are using MFC, check out CPropertyPage::SetModified().

"A good athlete is the result of a good and worthy opponent." - David Crow

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

littleGreenDude17-Aug-07 2:34

17-Aug-07 2:34

Thanks for the suggestion, but it didn't work.

The problem I have is that the screen fields aren't one-to-one with the recordset datafields. I have a single field in the recordset called ProductUse, and this is represented on the screen by 3 checkboxes, one for each of the following; ordering, receiving, counting. So, the dataset has 26 fields, and the form has 28 fields.

David Crow17-Aug-07 2:40

17-Aug-07 2:40

I fail to see the correlation. If you make a change to a property page, you've made a change to a property page, regardless of any recordset that may be involved.

"A good athlete is the result of a good and worthy opponent." - David Crow

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

littleGreenDude17-Aug-07 5:28

17-Aug-07 5:28

just to add a little more background info/specifics

I've added the following to DoFieldExchange:

DFX_Long(pFX, _T("[ProductUse]"), m_ProductUse, AFX_DAO_DISABLE_FIELD_CACHE);

Which according to the MFC/DAO help says I should be able to manually set the field as dirty so it will be saved by doing the following

m_pSet->SetFieldNull(&m_pSet->m_ProductUse, FALSE);<br />
m_pSet->SetFieldDirty(&m_pSet->m_ProductUse, TRUE);

As I mentioned before, the ProductUse field is actually derived from 3 checkboxes on the dialog, one for each of the following ORDERING, RECEIVING, COUNTING. So, as an example, my logic for the user clicking on the Receiving checkbox is as follows:

void cPgInvGenInfo::OnChkReceiving() <br />
{<br />
	m_pSet->SetFieldNull(&m_pSet->m_ProductUse, FALSE);<br />
	m_pSet->SetFieldDirty(&m_pSet->m_ProductUse, TRUE);<br />
<br />
	if( ((CButton*)GetDlgItem(IDC_CHK_RECEIVING))->GetCheck() )<br />
		m_pSet->m_ProductUse |= 00000010;<br />
	else<br />
		m_pSet->m_ProductUse &= 11111101;<br />
}

When I click close on the dialog, it happily closes without prompting to save changes, and exits without saving.

David Crow17-Aug-07 5:38

17-Aug-07 5:38

Why not use:

void cPgInvGenInfo::OnChkOrdering() 
{
    SetModified();
}
 
void cPgInvGenInfo::OnChkReceiving() 
{
    SetModified();
}
 
void cPgInvGenInfo::OnChkCounting() 
{
    SetModified();
}
 
void cPgInvGenInfo::OnOK() 
{
    // save canges to record set
}

"A good athlete is the result of a good and worthy opponent." - David Crow

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

CDialog SetParent

mcsherry14-Aug-07 4:17

mcsherry

14-Aug-07 4:17

I want to change the parent of a dialog so that its parent is the top level dialog (i.e. my main app). What is the correct way of doing this as when I get a pointer to the main dialog and use that the main app stops refreshing its display.

What I want is something like this:
MainApp->Modeless Dialog->Modeless Dialog->Modal Dialog attached to MainApp

I can get this working by callbacks through the code but thought that by simply doing modal_dialog->SetParent ( main_app ) would have the same effect but it doesn't.

cheers,
Andy

Re: CDialog SetParent

Maxwell Chen14-Aug-07 4:58

Maxwell Chen

14-Aug-07 4:58

Use the ctor.
CDialog::CDialog (MFC)[^]

explicit CDialog(
   LPCTSTR lpszTemplateName,
   CWnd* pParentWnd = NULL 
);
explicit CDialog(
   UINT nIDTemplate,
   CWnd* pParentWnd = NULL 
);

Maxwell Chen

Re: CDialog SetParent

mcsherry14-Aug-07 5:07

mcsherry

14-Aug-07 5:07

thank you, should have thought of that myself rather than looking at more complicated ways of doing it.

many thanks

Calling Convension

Programm3r14-Aug-07 3:48

Programm3r

14-Aug-07 3:48

Hi all,

What is the use of the __fastcall calling convention ?

Many Thanks
Regards,

The only programmers that are better that C programmers are those who code in 1's and 0's Green Alien | [Alien]

Programm3r
My Blog: ^_^

Iain Clarke, Warrior Programmer

Iain Clarke, Warrior Programmer14-Aug-07 3:51

14-Aug-07 3:51

http://en.wikipedia.org/wiki/X86_calling_conventions#fastcall[^]

Iain.

Programm3r14-Aug-07 4:14

Programm3r

14-Aug-07 4:14

Thanks Iain for the link Smile | :)

Regards,

The only programmers that are better that C programmers are those who code in 1's and 0's Green Alien | [Alien]

Programm3r
My Blog: ^_^

Nemanja Trifunovic14-Aug-07 4:03

Nemanja Trifunovic

14-Aug-07 4:03

Calling Conventions Demystified[^]

Programming Blog
utf8-cpp

Programm3r14-Aug-07 4:13

Programm3r

14-Aug-07 4:13

Thank you for the link Smile | :)

Regards,

The only programmers that are better that C programmers are those who code in 1's and 0's Green Alien | [Alien]

Programm3r
My Blog: ^_^

Dialog box Communication

sofa_2006au14-Aug-07 3:29

sofa_2006au

14-Aug-07 3:29

I have a "Dialogbox program" COriginDlg
I want to open a new dialog box CNewDlg -> using doModal()

In the new dialog box I want to access the original dialog box's variables etc.
Is this possible ??

WHen I try the following

BOOL CNewDlg::OnInitDialog()
{
CDialog::OnInitDialog();

COriginDlg dlg ; <------ ????

int i = dlg.Len ; <----- Try to access the variable 'Len' which is part of the class COriginDlg
< ERROR generated is "ACCESS VIOLATION" ???????
}

Any Ideas on how to do this properly ?

led mike14-Aug-07 4:16

led mike

14-Aug-07 4:16

sofa_2006au wrote:
I want to access the original dialog box's variables

That is a mistake. See Model-View-Controller Design Pattern[^]

Hamid_RT14-Aug-07 6:16

Hamid_RT

14-Aug-07 6:16

Does COriginDlg derived of CDialog?

WhiteSky

sofa_2006au14-Aug-07 6:25

sofa_2006au

14-Aug-07 6:25

Thanks for the reply.

Yes I think both are derived from CDialog

Both have:

class COriginDlg : public CDialog
class CNewDlg : public CDialog
------

Should I have derived CNewDlg from COrginDlg ???

David Crow14-Aug-07 7:50

14-Aug-07 7:50

sofa_2006au wrote:
Should I have derived CNewDlg from COrginDlg ???

Only if CNewDlg is a COrginDlg.

"A good athlete is the result of a good and worthy opponent." - David Crow

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