Forum

In VC6 Resource, I set a group box horizontal alignment to right,

after I use CExtGroupBox instead of CStatic to implement the groupbox, the horizontal alignment no longer work.

Any suggestion?

Thanks

Hi,

I have a MFC dialog-base project, and I’m trying apply skin to the main dialog CSPSSelection,
In SPSSelection.h, I write
class CSPSSelection:public CExtNCW < CExtResizableDialog>
{
CSPSSelection(CWnd* pParent = NULL); // standard constructor
....
}

but I got compile error in SPSSelection.cpp:
SPSSelection.cpp(31)
error C2614: ’CSPSSelection’ : illegal member initialization: ’CExtResizableDialog’ is not a base or member



this is my code:
CSPSSelection::CSPSSelection(CWnd* pParent /*=NULL*/)
    : CExtResizableDialog(CSPSSelection::IDD, pParent)
{
    //{{AFX_DATA_INIT(CSPSSelection)
    //}}AFX_DATA_INIT
}

How to fix this?
thanks

Please replace the following code:

CSPSSelection::CSPSSelection(CWnd* pParent /*=NULL*/)
    : CExtResizableDialog(CSPSSelection::IDD, pParent)
{
    //{{AFX_DATA_INIT(CSPSSelection)
    //}}AFX_DATA_INIT
}

with:

CSPSSelection::CSPSSelection(CWnd* pParent /*=NULL*/)
    : CExtNCW < CExtResizableDialog > ( CSPSSelection::IDD, pParent )
{
    //{{AFX_DATA_INIT(CSPSSelection)
    //}}AFX_DATA_INIT
}

Done,
I changed my code to
CSPSSelection::CSPSSelection(CWnd* pParent /*=NULL*/)
    : CExtNCW < CExtResizableDialog > ( CSPSSelection::IDD,pParent )

Got another question, some MFC resource Properties seems not work after migrate to prof-uis control.
for example,control order property and Transparent property

I have a MDI application with MDI Tabs. Each MDI Child Window contains an CExtResizableDialog dialog box that overlaps the entire client area of the MDI Child Window. The some child dialogs contain TAB controls with static and radio-button controls that do not draw properly when the application run under Windows XP with a theme enabled (they appear black). I found a work around on the problem (see the code below), but when I resize the application controls on the bottom side of the window are still painted black. The application was originally developed without Prof-UIS and I cannot replace all static and radio-buttons because I have hundreds of windows to change, not only this, dialogs may contain some custom ActiveX controls that have the same problem.
How can I manage to create a dialog window that has a bitmap background and transparent static, checkbox, ActiveX and radio-button controls with Prof-UIS ?
I mean, I would like to create an application with custom themes (not only Windows XP themes) using bitmaps as background of CExtResizableDialog dialogs, at the same time, I would like to have the possibility to use Prof-UIS controls, Windows controls and ActiveX controls in my CExtResizableDialog derived windows.

void CDlgProtect::UpdateBackgroundBrush(void)
{
    if (m_bThemeActive == 0)
    {
        HMODULE hinstDll;

        // Check if the application is themed
        hinstDll = LoadLibrary(_T("UxTheme.dll"));
        if (hinstDll)
        {
            typedef BOOL (*ISAPPTHEMEDPROC)();
            ISAPPTHEMEDPROC pIsAppThemed;
            pIsAppThemed = (ISAPPTHEMEDPROC) ::GetProcAddress(hinstDll, "IsAppThemed");

            if(pIsAppThemed)
                m_bThemeActive = pIsAppThemed() ? 0xFF: 1;

            FreeLibrary(hinstDll);
        }
    }

    // Destroy old brush
    m_brushCtrls.DeleteObject();

    // Only do this if the theme is active
    if (m_bThemeActive && !m_bmpBackImage.m_hObject)
    {
        CRect rc;
        CDC memDC;

        GetClientRect(rc);
        m_bmpCtrlsBackground.DeleteObject();
        
        CDC *pdcDlg = GetDC();
        memDC.CreateCompatibleDC(pdcDlg);
        m_bmpCtrlsBackground.CreateCompatibleBitmap(pdcDlg, rc.Width(), rc.Height());
        CBitmap *pOldBmpDest = memDC.SelectObject(&m_bmpCtrlsBackground);
        ReleaseDC(pdcDlg);
        g_PaintManager->PaintControlBarClientArea(memDC, rc, this);
        m_brushCtrls.CreatePatternBrush(&m_bmpCtrlsBackground);
        
        memDC.SelectObject(pOldBmpDest);
    }
}

HBRUSH CDlgProtect::OnCtlColor(CDC* pDC, CWnd *pWnd, UINT nCtlColor)
{
    if (m_bThemeActive)
    {
        CString sClassName;
        GetClassName(*pWnd, sClassName.GetBuffer(128), 128);
        sClassName.ReleaseBuffer();
        if (sClassName.CompareNoCase(_T("button")) == 0 ||
            sClassName.CompareNoCase(_T("static")) == 0 ||
            sClassName.CompareNoCase(_T("#32770")) == 0)//Dialog
        {
            RECT rc;

            // Set the background mode to transparent
            pDC->SetBkMode(TRANSPARENT);

            pWnd->GetWindowRect(&rc);

            // Map coordinates to the upper left corner of parent dialog window
            ScreenToClient(&rc);

            // Adjust the position of the brush for this control (else we see the top left of the brush as background)
            VERIFY(SetBrushOrgEx(*pDC, -rc.left, 0, NULL));
            
            return m_brushCtrls;
        }        
    }
    else
    {
        CString sClassName;
        GetClassName(*pWnd, sClassName.GetBuffer(128), 128);
        sClassName.ReleaseBuffer();
        if (sClassName.CompareNoCase(_T("static")) == 0 ||
            sClassName.CompareNoCase(_T("#32770")) == 0)//Dialog
        {
            pDC->SetBkMode(TRANSPARENT);
            return (HBRUSH)GetStockObject(NULL_BRUSH);
        }
    }
    return CExtResizableDialog::OnCtlColor(pDC, pWnd, nCtlColor);
}

While working with MDI_DynamicInnerOuterBars example I noticed that if you right click on "Outer Dynamic Bars" you get popup with options of (Float/Dock/tabbed document/hide). However if you rightclick "MDIDOC1" you dont get that popup. Is there an easy option to enable popup MDIDOC1.

MDIDOC1 is associated with the simple MDI child frame window which is a completely different type of window. Why do you think it should have that menu?

Well you are limited to MainFrame Client screen area for all simple MDI child frames. Any child window that goes out, is clipped. This limits it usage in Multi-Monitor cases. However if you have Float option, like the one you have for OuterBars then you can easily move that window across monitors.

Hi,

Just want to know is there any sample project demonstrate how to apply skin to CFormView? I put the formview into the CMDIFrameWnd
and if I can apply skin to my owner-draw CTabCtrl? I did repaint for the tab control.

Thanks

First of all, you need to make your form look consistent with the currently applied theme. This is described in the FAQ How to make CFormView to be look and act like CExtResizableDialog?. After that, the skin background will automatically be applied to your form view.

Prof-UIS provides a tab page container control implemented in the CExtTabPageContainerWnd class (the derived classes are CExtTabPageContainerOneNoteWnd, CExtTabPageContainerWhidbeyWnd and CExtTabPageContainerFlatWnd). This control is a container for several page windows (usually dialogs) and it uses the Prof-UIS tab window for switching the active page window. You can find it in the TabPages and ProfUIS_Controls samples. So, just use the tab page container instead of CTabCtrl. The CTabCtrl control is incompatible with Prof-UIS themes. It is just a wrapper around the tab common control. And the CExtTabPageContainerWnd class is written from scratch and provides many useful features including support for themes skins.

Thank you for your reply,

I have create a class CLeftTab which derived from CTabCtrl, and use ModifyStyle() to make the tabs position at left side, meantime the tab title is still keep horizontal orientation, and I put this control and some button into my CMainView which derived from CFormView.
In addition, I re-paint CMainView and CLeftTab.


I got a problem after I apply AQUA style skin:
CExtButton with AQUA style has a beautiful round corner, As I have to re-paint CMainView and CLeftTab, the CExtButton with AQUA style display with blemish outside of the round corner, I mean it no match the owner-drawed background of CMainView or CLeftTab.
Can I remove the blemish outside of the round corner?

Is there any CExtTabxxxx support left side tab with horizontal orientation title?

Can I just keep my MFC derived class and write hybrid code?

I use PatternBrush to paint my CLeftTab’s background with AQUA pattern, now the CExtButton looks comfortable with the container.

I’m use CExtBarUndoRedoButton derived class to implement undo button in my application.
Button has SeparatedDropDown style, so list box opened by click on dropdown arrow.
I want to close listbox by clickig again on dropdown arrow (as in MS Visual Studio) or on undo arrow.
How can i do it?

Thanks.

Thank you for your comment. Please update the CExtPopupControlMenuWnd::_OnMouseClick() method’s source code in the ../Prof-UIS/Src/ExtPopupCtrlMenu.cpp file:

bool CExtPopupControlMenuWnd::_OnMouseClick(
    UINT nFlags,
    CPoint point,
    bool & bNoEat
    )
{
    ASSERT_VALID( this );
    bNoEat;
    if( GetSafeHwnd() == NULL )
        return false;
    if( GetSite().GetAnimated() != NULL )
        return true;
CExtPopupMenuSite & _site = GetSite();
    if(    _site.IsShutdownMode()
        || _site.IsEmpty()
        || _site.GetAnimated() != NULL
        )
        return true;
    if( _IsTearOff() && CExtPopupMenuWnd::_HitTest(point) == IDX_TEAROFF )
    {
        bool bLButtonUpCall =
            (nFlags==WM_LBUTTONUP || nFlags==WM_NCLBUTTONUP)
                ? true : false;
        if( ! bLButtonUpCall )
            _DoTearOff();
        return true;
    }
CPoint ptScreenClick( point );
    ClientToScreen( &ptScreenClick );
HWND hWndFromPoint = ::WindowFromPoint( ptScreenClick );
    if(       hWndFromPoint != NULL
        &&    (::GetWindowLong(hWndFromPoint,GWL_STYLE)&WS_CHILD) != 0
        &&    (    m_hWndChildControl == hWndFromPoint
              ||   ::IsChild( m_hWndChildControl, hWndFromPoint )
              )
        )
    {
        bNoEat = true;
        return false;
    }
HWND hWndFocus = ::GetFocus();
    if(       hWndFocus != NULL
        &&    (::GetWindowLong(hWndFocus,GWL_STYLE)&WS_CHILD) != 0
        &&    (    m_hWndChildControl == hWndFocus
              ||   ::IsChild( m_hWndChildControl, hWndFocus )
              )
        )
    {
        bNoEat = true;
        return false;
    }
HWND hWndCapture = ::GetCapture();
    if(       hWndCapture != NULL
        &&    (::GetWindowLong(hWndCapture,GWL_STYLE)&WS_CHILD) != 0
        &&    (    m_hWndChildControl == hWndCapture
              ||   ::IsChild( m_hWndChildControl, hWndCapture )
              )
        )
    {
        bNoEat = true;
        return false;
    }
bool bPtInWndArea = _PtInWndArea( point );
    if( bPtInWndArea )
    {
        if( m_bExcludeAreaSpec )
        {
            CRect rc = m_rcExcludeArea;
            ScreenToClient( &rc );
            if( rc.PtInRect( point ) )
            {
                bPtInWndArea = false;
                bool bLButtonDownCall =
                    ( nFlags == WM_LBUTTONDOWN || nFlags==WM_NCLBUTTONDOWN )
                        ? true : false;
                if( bLButtonDownCall )
                {
                    _OnCancelMode();
                    return false;
                }
            }
        }
    }
    if( ! bPtInWndArea )
    {
        if(     m_pWndParentMenu != NULL
            &&  m_pWndParentMenu->GetSafeHwnd() != NULL
            )
        {
            ASSERT_VALID( m_pWndParentMenu );
            ClientToScreen( &point );
            m_pWndParentMenu->ScreenToClient( &point );
            HWND hWndOwn = GetSafeHwnd();
            ASSERT( hWndOwn != NULL );
            ASSERT( ::IsWindow(hWndOwn) );
            CExtPopupMenuWnd * pWndParentMenu = m_pWndParentMenu;
            bool bInplaceControlArea = false, bInplaceDropDownArea = false;
            int nHtTemp =
                pWndParentMenu->_HitTest(
                    point,
                    &bInplaceControlArea,
                    &bInplaceDropDownArea
                    );
            if( nHtTemp >= 0 )
            {
                MENUITEMDATA & mi = pWndParentMenu->ItemGetInfo( nHtTemp );
                if(        mi.IsPopup()
                    &&    mi.GetPopup() == this
                    )
                {
                    if( bInplaceControlArea )
                    {
                        pWndParentMenu->_SetCapture();
                        pWndParentMenu->_ItemFocusCancel( FALSE );
                        pWndParentMenu->_ItemFocusSet( nHtTemp, FALSE, TRUE );
                        if( mi.IsAllowInplaceEditActivation() )
                        {
                            CWnd * pWndInplace = mi.GetInplaceEditPtr();
                            if( pWndInplace != NULL )
                            {
                                ASSERT_VALID( pWndInplace );
                                ASSERT( pWndInplace->GetSafeHwnd() != NULL && (::IsWindow(pWndInplace->GetSafeHwnd())) );
                                if( (pWndInplace->GetStyle() & WS_VISIBLE) == 0 )
                                {
                                    CRect rcInplaceEdit;
                                    pWndParentMenu->_GetItemRect( nHtTemp, rcInplaceEdit );
                                    rcInplaceEdit =
                                        mi.AdjustInplaceEditRect(
                                            rcInplaceEdit,
                                            OnQueryLayoutRTL()
                                            );
                                    pWndInplace->SetWindowPos(
                                        NULL,
                                        rcInplaceEdit.left, rcInplaceEdit.top,
                                        rcInplaceEdit.Width(), rcInplaceEdit.Height(),
                                        SWP_NOZORDER|SWP_NOOWNERZORDER
                                            |SWP_NOACTIVATE|SWP_SHOWWINDOW
                                        );
                                }
                                pWndInplace->SetFocus();
                            }
                        }
                    }
#if (!defined __EXT_MFC_NO_CUSTOMIZE)
                    CExtCustomizeCmdTreeNode * pNode = mi.GetCmdNode();
                    if( pNode == NULL )
                        return true;
                    if( (pNode->GetFlags()&__ECTN_TBB_SEPARATED_DROPDOWN) )
#endif
                        return true;
                }
            }
            if( pWndParentMenu->_OnMouseClick(
                    nFlags,
                    point,
                    bNoEat
                    )
                )
            {
                if( bNoEat )
                    return false;
                if( ::IsWindow(hWndOwn) )
                    CancelMenuTracking();
                return true;
            }
            return false;
        }
        if(      nFlags == WM_RBUTTONUP
            ||   nFlags == WM_LBUTTONUP
            )
            return true;
        _OnCancelMode();
        return false;
    }
bool bRetVal = false;
    if(      m_hWndChildControl != NULL
        &&   ::IsWindow( m_hWndChildControl )
        )
    {
        CONTROLINPUTRETRANSLATEINFO _ciri(
            this,
            false,
            nFlags,
            point,
            bNoEat
            );
        bRetVal = 
            ( ::SendMessage(
                m_hWndChildControl,
                g_nMsgControlInputRetranslate,
                (WPARAM)(&_ciri),
                (LPARAM)0L
                ) != 0 )
            ? true : false;
    }
    return bRetVal;
}

I wanna use my own trackpopupmenu in a view.
But my MDI’s formview shows the submenu of "View".
How do I disable the default? or How do I pre-process my popup?

I made two resizable dialogs.
One is for main, the other is for reside in the main dialog(like your ProfUIS Control sample application).
Main dialog has a group-box which is used for position and sizing of the child dialog.
When I resize main dialog, child dialog remain it’s original position and size.
Both of are derived from CExtResizableDialog and anchored at OnInitDialog().
Do I need some other work to do it?

Initially you should use the group box control to position your child dialog(s) by invoking the MoveWindow() API. Then just anchor the child dialog inside the main dialog:

CExtResizableDialog * pMainDialog = . . .
CWnd * pGroupBox = . . . // something like pMainDialog->GetDlgItem( ID_MY_GROUP_BOX )
CExtResizableDialog * pChildDialog = . . .
CRect rc;
    pGroupBox->GetWindowRect( &rc );
    pMainDialog->ScreenToClient( &rc );
    pChildDialog->MoveWindow( &rc );
    pMainDialog->AddAnchor( pChildDialog->m_hWnd, __RDA_LT, __RDA_RB );

hi,

I have application that can switch to Full Screen mode and restore in normal state. In some situation automatically the application pass in full screen mode.
When I work in full screen mode I don’t wont some CExtControlBar object, to hide its I use ShowControlBar(...).
ShowControlBar method work only if the CExtControlBar object is docking or floating but when AutoHide is abilitated it daoesn’t work.
The only method I found is keep in memory the state of any CExtControlBar and if is in AutoHide mode I temporaly dock and then hide, I don’t think is the beauty method.

Could you have any suggestion to Show/Hide CExtControlBar when is in AutoHide mode? When the CExtControlBar hided is restored it have to return in AutoHide mode.

TX a lot for any response.

If you need to hide a simple control bar (not the dynamic control bar), you can do this with the following code:

CExtControlBar * pBar = . . .
CMainFrame * pMainFrame = . . .
    if( pBar->AutoHideModeGet() )
        pBar->AutoHideModeSet( false, false, true, true );
    else if( pBar->IsVisible() )
        pMainFrame->ShowControlBar( pBar, FALSE, FALSE );

The FullScreenState sample supports two independent control bar states for the normal and full screen modes. This allows you to avoid tracking the state of each bar. As a result, the end user can set up the layout of control bars in each mode independently from each other.

OK,
this work fine if I have bar objects created in CMainFrame window, but it seems does not work if I create a bars in CChildFrame.

Is a problem of my code or I have to use another method?

Thanks a lot

I’m using a CExtGridCell-based class (Prof-UIS 2.50) to implement an interface component. After the columns are layed out and the header created, code like the following is used to populate the cells.

    CExtGridCellString * pCellName =
    static_cast <CExtGridCellString *>
        (GridCellGet(
            1L,
            m_iKnt,
            0,
            0,
            RUNTIME_CLASS(CExtGridCellString),
            false,
            false
        ));    
    pCellName->TextSet(sName.c_str());

    if (m_bInRedo)
    {
        pCellName->BackColorSet(CExtGridCell::__ECS_NORMAL, sm_BkClrRedo);
        pCellName->BackColorSet(CExtGridCell::__ECS_SELECTED, sm_BkHiClrRedo);
    }
    else
    {
        pCellName->BackColorSet(CExtGridCell::__ECS_NORMAL, sm_BkClrUndo);
        pCellName->BackColorSet(CExtGridCell::__ECS_SELECTED, sm_BkHiClrUndo);
    }

This code works fine and appears to set the background colors as desired (i.e., there is no failure so long as the window is not visible), but when the window becomes visible, I get a "Debug Assertion Failed" message. It seems to be this ASSERT in CExtGridCell::OnQueryBackColor():

    if( clrBack != COLORREF(-1L) )
    {
        DWORD dwSiwStyleEx = wndGrid.SiwGetStyleEx();
        ASSERT( ( dwSiwStyleEx & (__EGBS_EX_HVI_EVENT_CELLS|__EGBS_EX_HVO_EVENT_CELLS) ) != 0 );
        return clrBack;
    }

It is the case that neither of these options are not set, but I’m (currently) not interested in hovering behaviour, just customizing the normal and selected background colours. NOTE: Non-debug builds exhibit no problems, and the grid appears and behaves as expected. Suggestions?

1) In my initial post I neglected to include the most important code, that which sets the styles:


        SiwModifyStyle(
                __ESIS_STH_ITEM
            |    __ESIS_STV_ITEM
            | __EGBS_SFB_FULL_ROWS
            | __EGBS_GRIDLINES
            | __EGBS_NO_HIDE_SELECTION    
            ,
            0,
            false
            );

        SiwModifyStyleEx(
            __EGBS_EX_CELL_EXPANDING_OUTER_B
            ,
            0,
            false
            );

        BseModifyStyle(
        0L
        ,
        __EGWS_BSE_DEFAULT,
        false
        );

2) I tried OR’ing EGBS_EX_HVI_EVENT_CELLS with the SiwModifyStyleEx() arg, and, sure enough, the problem went away!

This is good, but is still magic to me. Any information that might clarify what styles are required when would be greatly appreciated.

Hi,

I got an CExtButton display problem. the CExtButton dispear after the application be switched off and switched back using ALT+TAB if meantime the CExtButton mouse overed. but CButton do not has this problem. There are two conditions cause problem:
1.CExtButton be mouse overed.
2.Main application be switched off and switched back.

My project is a single document application without document/view architecture support. I create class CMainView which inherited from CFormView as the main view of the application.
And I put three controls in CMainView, they are CExtButton, CButton and a user-created CLeftTab which inherited from CTabCtrl. And, CMainView contains CLeftTab, and CLeftTab contains CExtButton and CButton.

I have to mention that CLeftTab and CMainView was redrawed by OnPaint(), both of them use GetClientRect() and FillRect() to redraw the background.

Does my code conflicts with CExtButton? Any suggestion would be appappreciated.

Thanks

What worked for me was removing WS_CLIPSIBLINGS from the ModifyStyle() call in CExtButton::PreSubclassWindow(). Then my group box could proceed the "child" controls in tab order as well.

I am getting close to the bug, I think the CLeftTab conflicts with CExtButton.
when I move the CExtButton out of the CLeftTab, there is no dispear problem.

CLeftTab and CMainView redraw function removed, problem still exists.

The problem can be easily fixed. First of all, please add the WS_CLIPSIBLINGS and WS_CLIPCHILDREN styles to the dialog template resource used by your form view window. Second, if there are some group boxes in this dialog template resource, please check the tab order for all the controls. The tab order number of each group box control should be greater that the tab order of any control "inside" the group box. Third, if your form view window is based on the CExtWS template class and enabled for horizontal and/or vertical scrolling, then you should handle the WM_HSCROLL and WM_VSCROLL standard Windows messages and repaint all the content including the form view window itself and all the child windows.

I send a email attached my project to ’support@prof-uis.com’ before I received this tech support.

In the attached project I put three controls in CMainView, they are CExtButton, CButton and CTabCtrl. And, CMainView contains CTabCtrl, and CTabCtrl contains CExtButton and CButton.

And the problem in attached project was fixed by followed the first two point in tech support.

But the problem still exists in the original project.

Hi:
I would like to create a grid cell with a slider to control image opacity. CExtGridCellSlider seems to be appropriate but I haven’t seen any samples that use it nor any documentation on it in the help file. Do you have information on this class available?

Thanks
BobSabiston

I made a CExtGridWnd derived class ( likes the sample SimpleGrid ).
Add a owner-drawn control into a formview, and subclassed the control into the class.

In a Formview’s function, I add some lines into the control.
The problem is : the function works for a long time, so, I wanna view each added line when the line is added.
But, before the function return, lines are not shown at all(only scroll bar is redrawn).

How do I force the added line be drawn on the control?

Hi,

I have got a derived class from CExtToolControlBar.
In this class there is a function to insert btns dynamicly.
e.g.
CMyToolBar::InsertBtn() {
....
// register new special character
if( nBtnCmdID >= nBtnCmdIDMin && nBtnCmdID <= nBtnCmdIDMax ) {
// register new cmd for btn
CExtCmdItem *pCmdItem = g_CmdManager->CmdAllocPtr( lpszProfileName, nBtnCmdID );
ASSERT( pCmdItem != NULL );
if( pCmdItem != NULL ) {
CString ToolTip = pSCBtn->m_SpecialChar.HexCode + _T(" ") + pSCBtn->m_SpecialChar.Description;
pCmdItem->m_sTipTool = ToolTip;
pCmdItem->m_sTipStatus = ToolTip;
pCmdItem->m_sToolbarText = pSCBtn->m_SpecialChar.cChar;
pCmdItem->m_sMenuText = pSCBtn->m_SpecialChar.cChar;

// add btn to toolbar
pSCBtn->SetCmdID(nBtnCmdID);
VERIFY( InsertButton( -1, ID_SEPARATOR) );
VERIFY( InsertSpecButton( -1, pSCBtn) );


Customization is enabled and the toolbar is registered.

How can I add the dynamicly created buttons to customization subsystem
(like in CExtCustomizeSite::OnRegisterToolBar)?

Thank for any help.
Michael

Hi,
I have an MDI application with CExtTabMdiOneNoteWnd control in CMainFrame.
In some case active view can switch in full screen mode, there is a method to temporaly hide the all tabs in CExtTabMdiOneNoteWnd ?
I wish to hide tabs when view switch in full screen mode and show its when view is restored in normal state.

Thanks a lot

HI,
I have an MDI application with CExtTabMdiOneNoteWnd.
I wish draw client area, of CView derived class, with color of current tab, in OnPaint function. How can I retrieve this color?

TX a lot

This is actually a PhotoShop sort of question, not a Prof-UIS question; but I’m hoping someone can help me here. My app allows the user to choose different color themes. The edges of some of my buttons do not blend well against incompatible colors. I need some of the edge pixels to be some sort of percentage blend between the background color and a foreground color. Is there a way I can use PhotoShop to create edges that do this sort of blending?

My application was calling CMDIFrameWnd::RecalcLayout multiple times in a transaction, when only one final call was really needed. I suspect that I had this problem before I initroduced Prof-UIS into the application. But the extra calls to RecalcLayout noticeably slowed down the application when Prof-UIS was introduced. Also, the control bars would shuffle around, creating a distraction for the user.

I think I found a way to work around this problem. It might be even better than a work-around. It might actually be a good solution. I’d be interested in Prof-UIS Support’s opinion of this:

1. Add a BOOL m_bPendingPostMessage member to the CMainFrame.

2. In the CMainFrame, override CMDIFrameWnd::RecalcLayout:

void CMainFrame::RecalcLayout(BOOL bNotify)
{
    if (!m_bPostMessageRecalcLayoutPending)
    {
        m_bPostMessageRecalcLayoutPending = TRUE;
        PostMessage(WM_USER_PENDING_RECALC_LAYOUT, bNotify);
    }
}

3. Handle the WM_USER_PENDING_RECALC_LAYOUT message as follows:

LONG CMainFrame::OnPendingRecalcLayout(UINT wParam, LONG)
{
    CMDIFrameWnd::RecalcLayout((BOOL)wParam /* bNotify */);
    m_bPostMessageRecalcLayoutPending = FALSE;
    return 0;
}


The control bars have really "calmed down" once I did this. It was such a easy solution, compared to hunting down all of the cases where there were redundant calls to RecalcLayout. I believe this solution does more than what the MFC CFrameWnd::m_bInRecalcLayout does, which is apparently to just avoid recursive calls, perhaps infinitely recursive calls.

Please let me know if you see any flaws in this.

Cheers
-- Mark

I believe the progress bar cell type shipped in the latest release is a very useful addition to the Prof-UIS suite.

I am wondering whether you intend to provide more controls supporting background tasks like open ended processes (e.g., processes whose ends cannot be determined at their start time)?!

A good example in this direction is the progress bar used by ’Incredibuild ’(a plug-in for Visual Studio that performs compilations spread across multiple machines).

I e-mailed you a Visio document where providing more details.

I would really appreciate I short answer providing some guidance ( like, "no, it is not our intention" or "possibly, next year/quarter", etc.)

Thanks,

Emil

Is there an easy way of making the CExtEdit control act the same as the CExtGridCellCurrency?
Thanks in advance,
Eddie