PropertyPage OnInitDialog

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We or I am evaluating the ToolkitProEval.MFC.v15.3.1 MFC controls integrated in VS 2010. My question concerns the implementation in a derived PropertyPage where we have derived sheets and views and out PropertyPages, Sheets and Views derive from a CBasePage or CBasSheet or CBaseView which all eventually derive from the MFC CPropertyPage, CPropertySheet and CPropertyView classes. Property pages seem at first glance to be similar to CDialog but could be mistaken.
We would like to use the ReportControl to create more than 255 controls on a page (MFC limit is 255) and render different controls in the row/column cell matirx. Using the ReportDemo as a basis of how to implement is different in our MFC project's behavior. The ReportDemo sample appears to use an ICustomControl that is classed to XTPReport. We are only adding columns at this point in the OnInitDialog method but can not get to the OnInitDialog derived method. This is not clear why the missing call unless a resource or class is not being created, found...

Our evaluation experience is the derived OnInitDialog method is not called when we use the ICustonControl and this custom control takes over the entire property page including the tab (title) area. From appearances and previous implementation our derivation is working without the custom control. 

The CreateIndirect method in dlgcore is used which should call OnInitDialog, no message map needed.  Derived classes implement virtual methods OnSetActive, OnInitDialog DDX and call base classes as required. We have been using this architecture for quite some time through the various Visual Studio IDE's with no issue. We have not used the custom control ever.

I think where we are headed with this note is asking how to get off the ground implementing the ReportControl in a derived CPropertyPage versus the report sample dialog implementation.

Do we have the custom control resource set up correct?

Do we meet the ititial requirements to use CodeJock in our winapp (YES)?

Do we need to register a class and if so which one?

We can be more specific on questions related to the implementation if we understood where to focus the implementation attention. 

Is there a PropertyPage example? We would like to focus on where to make code adjustments but with MFC not sure what to do. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
MudHut Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 17 December 2012 Status: Offline Points: 1	Post Options Post Reply Quote MudHut Report Post Thanks(0) Quote Reply Topic: PropertyPage OnInitDialog Posted: 17 December 2012 at 11:44am
	We or I am evaluating the ToolkitProEval.MFC.v15.3.1 MFC controls integrated in VS 2010. My question concerns the implementation in a derived PropertyPage where we have derived sheets and views and out PropertyPages, Sheets and Views derive from a CBasePage or CBasSheet or CBaseView which all eventually derive from the MFC CPropertyPage, CPropertySheet and CPropertyView classes. Property pages seem at first glance to be similar to CDialog but could be mistaken. We would like to use the ReportControl to create more than 255 controls on a page (MFC limit is 255) and render different controls in the row/column cell matirx. Using the ReportDemo as a basis of how to implement is different in our MFC project's behavior. The ReportDemo sample appears to use an ICustomControl that is classed to XTPReport. We are only adding columns at this point in the OnInitDialog method but can not get to the OnInitDialog derived method. This is not clear why the missing call unless a resource or class is not being created, found... Our evaluation experience is the derived OnInitDialog method is not called when we use the ICustonControl and this custom control takes over the entire property page including the tab (title) area. From appearances and previous implementation our derivation is working without the custom control. The CreateIndirect method in dlgcore is used which should call OnInitDialog, no message map needed. Derived classes implement virtual methods OnSetActive, OnInitDialog DDX and call base classes as required. We have been using this architecture for quite some time through the various Visual Studio IDE's with no issue. We have not used the custom control ever. I think where we are headed with this note is asking how to get off the ground implementing the ReportControl in a derived CPropertyPage versus the report sample dialog implementation. Do we have the custom control resource set up correct? Do we meet the ititial requirements to use CodeJock in our winapp (YES)? Do we need to register a class and if so which one? We can be more specific on questions related to the implementation if we understood where to focus the implementation attention. Is there a PropertyPage example? We would like to focus on where to make code adjustments but with MFC not sure what to do.
	MudHut