Forum

Hi,

Using CExtResizable property sheet makes the property pages  to go out of boundary in some cases when used in our customized classes due to which the tab headers are not visible ( the tab headers get superimposed and when we pull the property page we get to see the tab headers). Is there a way to handle this scenarion 

Thanks, 

Howard  

Dear Support,

Would you be able to provide a simple sample according to your instruction above. I also need this kind of property dialog box.

I am looking forward to hearing from you soon

And also, would you be able to create links about all your small sample project that you have created on this forum for both general and support forum. I think this will be so helpful for people to learn your code in a simple way. I like the sample on your website but,it took sometimes to figure it out what i want. thank you.

You can see tab page containers with dialog pages in the Tab Containers dialog page of the ProfUIS_Controls sample application. The same can be created using a simpler dialog window layout. I.e. One modal dialog window with CExtTabPageContainerWnd and OK, Cancel, Help buttons. Several dialog or other windows should be created as children of the CExtTabPageContainerWnd window. This simple window layout emulates a classic resizable property sheet in tabbed mode. But you can use CExtResizablePropertySheet and CExtResizablePropertyPage controls of Prof-UIS 2.90 as is because they also support a themed tab control.

Current versions of the CExtResizablePropertySheet and CExtResizablePropertyPage classes are designed for property sheets in the Wizard mode (i.e. without visible tab common control). If you need tabbed property sheets, then please use the following UI design:

1) Create popup dialog (resource and C++ class) with CExtTabPageContainerWnd control, OK, Cancel and other needed buttons. Tab page container can be either created in OnInitDialog() method or inserted as custom control into dialog template resource. You can find tab page containers as custom controls in the ProfUIS_Controls sample application.

2) Create several child dialogs (resources and C++ classes) implementing pages. These dialogs should have both Child and Visible properties of dialog template resource set on.

3) Initialize dialog pages in the OnInitDialog() virtual method of popup dialog. Dialog pages should be created as children windows of the CExtTabPageContainerWnd window. Then you should register them as pages with invocation of the CExtTabPageContainerWnd::PageInsert() method.