Professional UI Solutions
Site Map   /  Register


Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Prof-UIS General Discussion » Implementing Prof-UIS into and exisitng project Collapse All
Subject Author Date
John Fliczuk Jun 12, 2009 - 11:14 PM

I have an existing MFC project which has some very old code in it. When I updated to visual studio 2008 I found some things didn’t work anymore. I need to upgrade becuase I want access to some of the stuff in the new MFC Library. I figure this would be a great time to replace some of the non-functioning code with Prof-UIS code as well.

I don’t have a lot of C++ or MFC experience so this may be a problem. I do have a lot of programming experince so I’m not a complete newby.

I wanted to replace a treelist with a tabedcombobox. To start I thought I would just try adding tabedpages. I’m finding this very difficult. The sample code is not well documented and I’m having trouble understanding the code and how I might integrate it into my app. I tried adding 2 files to my project. CExtTabPageContainerWnd.cpp / .h. I didn’t change any code and tried to compile.

This is the error I got which I can’t even see how it relates to the code.

C:\Program Files\FOSS Software Inc\Prof-UIS\Include\ExtPopupMenuWnd.h(112) : error C2504: ’CEvent’ : base class undefined

That is just 1 of many error lines. As far as I know I have all my program/compile paths setup and I followed the install instructions for Prof-UIS. So I’m at a loss or just plain lost.

Any hep would help at this point. I think one of my biggest problems is lack of info and where to begin.


Mantra Jun 16, 2009 - 3:17 AM

if you need a example how to deal with this 

i have a Example which allows you to change it within minutes if you have

-> Tab sheets are Dialogbased

-> All your calls  inside the tabs are with a pointer..

let me know if you need id..



John Fliczuk Jun 13, 2009 - 4:15 PM


That helps a bit. i’m sure I have everything installed ok. The install took a couple of hours building libraries.

I want to replace the Tabed Pages part of my code since it actually stopped working when I ported from VS2005 to VS2008. Do I need to create the MainFrame Window using the Prof-UIS libs or can I add in the Tabed Pages part to my existing code? I am using SDI.

Also, is there any documentation that would better explain the Tabed Pages and how to implement it?

Thanks for you help...

Technical Support Jun 15, 2009 - 2:32 PM

You should create a CExtTabPageContanerWnd window (or any other derived from it) instead of the main SDI view window. The CExtTabPageContanerWnd window should be created using the AFX_IDW_PANE_FIRST standard MFC dialog control identifier. Then create your page windows as children of the CExtTabPageContanerWnd and register them as tab pages using the CExtTabPageContanerWnd::PageInsert() method. For instance, the TabbedBars application use the CExtTabPageContainerOneNoteWnd window as a child view window and creates 3 dialog pages inside it.

Technical Support Jun 13, 2009 - 12:37 PM

The source code of Prof-UIS is located in the folders .../Prof-UIS/Include and .../Prof-UIS/Src. You should not try to include any .../Prof-UIS/Include/Ext*.h header and .../Prof-UIS/Src/Ext*.* files into your project because they too muchdepend on each other. As a result, you would have to insert all the Prof-UIS files into your project. So, just include .../Prof-UIS/Include/Prof-UIS.h into the StdAfx.h file in your project:

#include <Prof-UIS.h>
This is the only thing you need to do to integrate Prof-UIS with the existing project. You don’t need to specify any Prof-UIS LIB files in your project settings because these files will be linked with your project automatically (Prof-UIS header files have appropriated #pragma directives for that). Of course, you should have Prof-UIS correctly installed, Visual Studio correctly configured and required Prof-UIS library configurations compiled. This is discussed here: