Forum

The CExtEdit class does not depend on the group box control in the same dialog template resource. Please run the ProfUIS_Controls sample application and check whether this bug exists in it. We believe there is no such a bug, so please compare the properties of your dialog resource with those in the ProfUIS_Controls project. Besides, check the mutual Z-order for the edit and group box. If the problem persists, just send us a test project.

Please note that this forum is about the Frame Features control. Prof-UIS General Discussion or Prof-UIS Tech Support Discussion are more appropriate topics for this message.

We think there is no reason not to use expanding pages because this may confuse the users of your application. If you need to prevent expanding, please add a handler for the WM_LBUTTONUP message like this:

void CYourPageContainerWnd::OnLButtonUp(
  UINT nFlags, CPoint point) 
 {
 PAGE_ITEM_INFO * pPageInfoToExpand = NULL;
 HIT_TEST_INFO _pht( point );
  PageHitTest( _pht );
  if( _pht.m_dwHitTestCode &
    _EPCHT_ON_PAGE_CAPT_ANY )
  {
   ASSERT( _pht.m_pPageInfo != NULL );
   if( _pht.m_pPageInfo ==
     m_pPageInfoPressed )
    pPageInfoToExpand =
     m_pPageInfoPressed;
  }
  if( pPageInfoToExpand != NULL )
  {
   // analyze the pPageInfoToExpand and
   // return if you need to cancel
   // page expanding
   return;
  }
  CExtPageContainerWnd::OnLButtonUp(
   nFlags, point );
 }

Dear Guido,

Thank you for your interest in Prof-UIS Frame Features!

We need to explain you behavior of SDI and MDI form windows with the Frame Features control inside.

In both cases Frame Features injects toolbars, menu bar, status bar and, optionally, MDI tabs. All these windows are placed close to the form window’s sides making the rest of form space in the center smaller. In case of MDI form, the center of the form is the MDI form container window (usually of the dark gray color) and it is repositioned automatically by Frame Features. You can make a tabbed MDI application with Frame Features and even keep all MDI child forms always maximized, but unfortunately you cannot inject any other window close to the MDI form container. This feature will be available in the next Frame Features releases after we add support for resizable panels.

We can offer you the following solution. Just use a child frame control in the SDI form and make Frame Features use it as a center window in the form. The child frame will fill all the main form space that is free of any bars. This child frame should contain the outlook bar and a tab control with pages inside.

We just published the first pre-release version of Frame Features and welcome you to post any questions and ideas you have about this ActiveX library!