Forum

First of all I would like to thank you very much for helping me with the issue that I am having regarding use PROF-UIF controls inside MFC dialogs. The fixed project file was helpful. Thank you, thank you, thank you!

For any PROF-UIF class, how do I find out the proper "class" name that needs to be put inside the custom control in the dialog? Where is documentation about this topic? Since, I can’t find any documentation, I am forced to guess, and this is not a good technical solution. Can you assist me with this problem also?

New issues keep comming up, and I require more technical support. I have revised the sample program and have uploaded it to the location http://www.optidoc.com/junk.zip. This is an MFC dialog application, where you click a button from the main dialog, to invoke a secondary dialog, say a preferences dialog. This sub dialog has the embedded control m_ExtTabPageContainerWnd as we had working in the main dialog last go around.

However, when this control is used inside a dialog (inside the main dialog) it fails to draw the panes. If the control is used within the main dialog, the panes draw properly. So, my project is stuck again until this issue can be resolved. Since working with a specific example proved valuable last go around, I have provided another example of this problem.

You will have to change the byte alignment from ZP1 to default for you to test. It is a requirement that all of my projects be built with ZP1 byte alignment, and I have rebuilt all of PROF-UIF with one byte alignment on my development machine. It would be nice to have an example of how this is done in your documentation, so that I can be sure that I have rebuilt everything properly. So, far the byte alignment has not been an issue.

Again, the example of the problem is located at http://www.optidoc.com/junk.zip

Thanks,

Miles Waldron

Advanced Technology Services, Inc.

 

Please try searching for the CLASS_NAME text in the .../Prof-UIS/Include folder and you will find definitions of all the window class names. Each window class name string is defined near corresponding C++ class.
For instance, the following class name is used by the CExtScrollItemWnd class and all the derived from it classes including grid controls (see also class hierarchy in Prof-UIS help):

#define __EXT_SCROLLITEMWND_CLASS_NAME _T("ProfUIS-ScrollItemWindow")

We fixed your test project. We set both the Clip Children and Clip Siblings properties of both the IDD_ANOTHERDIALOG and IDD_INSIDEPANEDIALOG dialogs to true. We set the Visible property of the IDD_INSIDEPANEDIALOG dialogs to true and we set its Style property to Child (the most critical issue). We also recommend you to replace the following line in the CAnotherDialog::OnInitDialog() method:

BOOL b1 = m_wndInsidePaneDialog.Create(CInsidePaneDialog::IDD);

With the following:

BOOL b1 = m_wndInsidePaneDialog.Create(CInsidePaneDialog::IDD, &m_ExtTabPageContainerWnd);

Nevertheless the CExtTabPageContainer::PageInsert() will change the parent window of inserted page window to the CExtTabPageContainer window, it’s correct to created window as child of tab page container window.
Here is the modified version of your test project:
http://www.prof-uis.com/download/forums/tmp/Junk2-fixed.zip