Pete2003
asked on
CPropertySheets and parent dialogs
Hi All,
I have a Parent CDialog.
This CDialog has a CPropertyPage
The CPropertyPage has two CPropertySheets
Now be it due to necessity or bad design on my part, i need to call a method (update some controls) on the parent CDialog from within my CPropertySheet.
The CPropertySheets are static CDialogs which are now inherited from CPropertySheet.
I have thought of passing the 'this' parameter in the property sheet constructor, but I get a circular error with the include files.
What would be the easiest solution for calling a member function of my parent CDialog from my CPropertySheet
Txs
I have a Parent CDialog.
This CDialog has a CPropertyPage
The CPropertyPage has two CPropertySheets
Now be it due to necessity or bad design on my part, i need to call a method (update some controls) on the parent CDialog from within my CPropertySheet.
The CPropertySheets are static CDialogs which are now inherited from CPropertySheet.
I have thought of passing the 'this' parameter in the property sheet constructor, but I get a circular error with the include files.
What would be the easiest solution for calling a member function of my parent CDialog from my CPropertySheet
Txs
ASKER
There is a guard already ... but because I'm using pointers to the classes inside the child classes the parent class is then undefined.
My question was however more specific. How can I make calls on the PropertyPage or even the parent dialog from the property sheet
My question was however more specific. How can I make calls on the PropertyPage or even the parent dialog from the property sheet
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok that wan't really help me since both these classes inherit from diffrent places so it's a bit more complicated, so I'll have to redesign ... but here are the points anyway :)
class CMyDialog;
class CMyPropertySheet {
};
Is there a guard around the header file?
#ifndef filename_h
#define filename_h
header file content.
#endif
This prevents the file from beeing included twice. I think the guard should always be present.
Do you really need a method of the parent to be called or would it be sufficient to post the parent a message?