Forum

Hello.

In IconEditor.
An afterimage remains when I move WindowA in a white line of CListBox
http://www.yukai.jp/~ifreeta/20080201/image02.jpg

Please teach an improvement method. (help me~)

This is a local problem in the custom drawn list box in the IconEditor sample application. We would like to ask you to use a CExtGridWnd control instead of list boxes and a list view in thereport mode to avoid any painting problems with custom drawn Win32 common controls.

Hello

Not a mouse, I want to change expression contents of these CExtBarButton by processing in the program.

http://www.yukai.jp/~ifreeta/20080201/image01.jpg

Thanks,

Your code looks absolutely correct. You can use the CExtToolControlBar::CommandToIndex() method instead of the for() loop in your ScanCommandItems() method.

Hello.

I seem not to be able to ask you a question well.
Not dynamic, I want to change it into appointed CmdID from the program inside.
I seem to be able to do it by the following programs.
If there is the method that is better than this, please teach it

    CExtBarButton * pExtBarButton;
    pExtBarButton = ScanCommandItems( nGrpCmdID );
    if ( pExtBarButton != NULL ){
        CExtRibbonButton * pNodeGrid;
        pNodeGrid = (CExtRibbonButton *)pExtBarButton;
        pNodeGrid->SetCmdID ( ID_LINE3 , true , true );
    }

----------------------------------------------------------------

CExtBarButton * CMuRibbonBar::ScanCommandItems( UINT nCmdID )
{

    if( ! IsVisible() )
        return 0;

    INT nBtnsCount = GetButtonsCount();
    if( nBtnsCount == 0 )
        return 0;

    INT nUpdateBtnsCount = 0;
    bool bUpdateBar = false;
    for( INT nBtnIdx = 0; nBtnIdx < nBtnsCount; nBtnIdx++ )
    {
        CExtBarButton * pTBB = NULL;

        pTBB = ( ( CExtRibbonPage * )( this ) ) -> GetButton( nBtnIdx );
        ASSERT_VALID( pTBB );
        UINT nTbbCmdID = pTBB->GetCmdID( false );
        if(    nTbbCmdID != nCmdID )
            continue;
        return pTBB;
    } // for( INT nBtnIdx = 0; nBtnIdx < nBtnsCount; nBtnIdx++ )

    return NULL;
}

The ribbon bar buttons display exactly the same menus like toolbar buttons. If you need fully dynamic menus, then you can choose one of the following ways:

1) Change command tree nodes describing popup menu structure under ribbon bar’s button.

2) Make this menu containing only one command item and handle the CExtPopupMenuWnd::g_nMsgPrepareMenu (or CExtPopupMenuWnd::g_nMsgPrepareOneMenuLevel) registered windows message like demonstrated in the ProfUIS_Controls sample application. This will allow you to find a single command item in a popup menu, remove it and insert a set of other menu items instead.

Hello.

I know how to use __ECTN_TBB_SEPARATED_DROPDOWN| __ECTN_TBB_AUTOCHANGE_ID.

What I want to hear.
It was generated in the ribbon bar inside.
pTBB = new CExtBarButton

With pTBB, I want to operate a menu from the program side.

hello, Support,

the rendering of the ribbon is OK with Normal Fonts on WindowsXP.
however, if to use large fonts setting (DPI properties of the screen in Windows XP) the layout is destroyed - it looks like it tries to show nodes in 4 rows (not in 3 as it was with small font).

how to make it use the same layout for LargeFonts settings as it is used for normal fonts?

thank you!

Vladimir

hi,

is it possible to change the way a bitmap is painted on a button ( CExtButton ) when the bitmap of a button ( m_icon ) has a larger size than the button. Currently prof-uis automatically centers the bitmap on the button ( we use prof-uis v282 )

CExtPaintManagerXP::PaintIcon(...)
{
....

        if(    ( _sizeIcon.cy + rcIconMargins.top + rcIconMargins.bottom ) > rcClient.Height() )
        {
            nIconAlignment &= ~__ALIGN_VERT_MASK;
            nIconAlignment |= __ALIGN_VERT_CENTER;
        }

...

        else if( (nIconAlignment&__ALIGN_VERT_MASK) == __ALIGN_VERT_CENTER )
        {
            rcIconLocation.OffsetRect( 0, ( rcClient.bottom - rcIconLocation.bottom ) / 2 + rcIconMargins.top - rcIconMargins.bottom );
        }

Now only the central portion will be painted : i.e. if the m_icon is a bitmap with a height of 100, and the button has a height of 50. Only the 25 - 75 portion of the bitmap will be displayed ( ignore the margin ).

how to disable this feature and make sure the top left corner of the bitmap always show up in the button ?

Thanks

You can find all the alignments and margins supported by button control in the ProfUIS_Controls sample (the Buttons page) . The button control can be painted as a colored rectangle with a single pixel border in one theme and as a bitmap based skin with a wide skinned border in other theme. We assume that button icons should be less than a button at least by two or three pixels. We can change the centering behavior for the button icon but in any case the icon that is larger than a button will have incorrect look under the most of themes. It would be extremely interesting to know more details about the button controls in your real project which need larger icons.

Hallo,
I would like to ask if it is possible to toggle a CExtControlBar just like a Toolbar from the view menu. The Toolbars have a check icon next to them in the View Menu while the control bar does not.
Also when I click the view menu entry it only shows the control bar (if I have closed it before) but does not hide it.
Any ideas?

Thank you for the help. I forgot to change a parameter in these functions. Your examples were most helpful and a solution was found.
Thank you for your time.

We can provide you with a relevant solution. For instance, the SDI sample application uses a check-like control bar menu commands for resizable control bars when the ProfStudio sample uses Visual Studio style commands. The difference between these applications are only in the OnBarCheck() and OnUpdateControlBarMenu() methods of the main frame class. If you provide us with a test project, we make any or all resizable control bars use menu commands like you need.

I think this answer is a copy of my other thread. This is not what I asked. Could you please provide a relevant answer?

The CExtPropertyGridCtrl class does not support print/preview. The CExtPPVW < CExtPropertyGridCtrl > template based class supports it. You should simply remove CExtPPVW from the declaration of the property grid control in your project.

Hallo again,
I don’t think you understood my question.
I am using these methods as your manual describes. In most of the cases they were automatically created by your wizard.
My question is, if I can Show and hide a control bar, by clicking the "view menu" entry that corresponds to that control bar, the same way I show and hide any other toolbar from the equivalent "VIEW menu" entry.
Up till now I can only show the control bar but cannot hide it from the View menu. If the control bar is already visible and I select it from the "View menu" it only gives it Focus instead of hiding it.

I have a class derived from CExtPropertyGridWndCategorized as I want to add sub categories only when the user presses expand for the first time.
My code seems to work, but I get an assert.

I get an assert in:
CExtTreeGridWnd::ItemEnsureVisibleBranch()
when it calls EnsureVisibleRow( nRowOffset, bRedraw ); with nRowOffset = -1.

I seem to be able to fix the assert by changing:
if( nRowOffset < rcVisibleRange.top )
{
EnsureVisibleRow( nRowOffset, bRedraw );
return;
}

to:
if( nRowOffset < rcVisibleRange.top )
{
if (nRowOffset!=(-1))
EnsureVisibleRow( nRowOffset, bRedraw );
return;
}

but as I’m not sure what this code is doing I’m not sure if it will have any side effects.
I can achieve this by overriding CExtTreeGridWnd::ItemEnsureVisibleBranch(), but is this the right thing to do?

My Grid Wnd is derived from CExtPropertyGridWndCategorized as follows:

class CExtPropertyGridWndCategorizedArc : public CExtPropertyGridWndCategorized
{
public:
CExtPropertyGridWndCategorizedArc(CExtPropertyGridCtrl* pPropertyGridCtrl = NULL)
: CExtPropertyGridWndCategorized(pPropertyGridCtrl) {}
virtual void ItemExpand(HTREEITEM hTreeItem, INT nActionTVE = TVE_TOGGLE,
bool bRedraw = true);
std::vector<HTREEITEM> m_vExpandedOnce;
};

void CArchivePropertyCtrl::CExtPropertyGridWndCategorizedArc::ItemExpand(HTREEITEM hTreeItem, INT nActionTVE, bool bRedraw)
{
CWaitCursor wc;
CExtPropertyItem* pItem = PropertyItemFromTreeItem(hTreeItem);
ASSERT(pItem);
bool bUpdated = false;
bool bExpanding = !pItem->ExpandedGet();
if ( bExpanding )
{
bool bFoundCategory=false;
int iCount = pItem->ItemGetCount();
for (int i=0; i<pItem->ItemGetCount(); i++)
{
CExtPropertyItem* pChild = pItem->ItemGetAt(i);
if (pChild->ItemGetCount()>0)
{
bFoundCategory = true;
break;
}
}
if (!bFoundCategory)
{
bUpdated = dynamic_cast<CArchivePropertyCtrl*>(m_pPropertyGridCtrl)->ExpandSubKey(*pItem, "", 1);
}
}

if ( bUpdated )
dynamic_cast<CArchivePropertyCtrl*>(m_pPropertyGridCtrl)->PropertyStoreSynchronize();
__super::ItemExpand(hTreeItem, nActionTVE, bRedraw);
}



this is the assert call stack:
>    ProfUIS281md.dll!CExtGridBaseWnd::EnsureVisibleRow(long nRowNo=-1, bool bRedraw=true) Line 6017 + 0x17 bytes    C++
    ProfUIS281md.dll!CExtTreeGridWnd::ItemEnsureVisibleBranch(_TREEITEM * hTreeItem=0x06f890a8, bool bRedraw=true) Line 3649 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtTreeGridWnd::ItemExpand(_TREEITEM * hTreeItem=0x06f890a8, int nActionTVE=2, bool bRedraw=true) Line 3624 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::ItemExpand(_TREEITEM * hTreeItem=0x06f890a8, int nActionTVE=2, bool bRedraw=true) Line 7320    C++
    GuiMdi.exe!CArchivePropertyCtrl::CExtPropertyGridWndCategorizedArc::ItemExpand(_TREEITEM * hTreeItem=0x06f890a8, int nActionTVE=2, bool bRedraw=true) Line 750 + 0x17 bytes    C++
    ProfUIS281md.dll!CExtPropertyItem::OnGridRowInitialized(CExtPropertyGridWnd & wndPG={...}, _TREEITEM * hTreeItem=0x06f890a8, CExtGridCell * pCellCaption=0x06fafea8, CExtGridCell * pCellValue=0x06fafef8) Line 838 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyItemInsert(CExtPropertyItem * pPropertyItem=0x06fa7110, long nIndex=9, _TREEITEM * htiParent=0x06f88c70, bool bRedraw=false) Line 6741 + 0x22 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyItemInsertAlphabetic(CExtPropertyItem * pPropertyItem=0x06fa7110, _TREEITEM * htiParent=0x06f88c70, bool bRedraw=false) Line 6788 + 0x22 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyStoreSynchronizeOneLevel(CExtPropertyItem * pPropertyItem=0x06fa7110, CExtPropertyItem * pParentItem=0x0470c280) Line 6571 + 0x1c bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyStoreSynchronizeOneLevel(CExtPropertyItem * pPropertyItem=0x0470c280, CExtPropertyItem * pParentItem=0x0470ccc0) Line 6629 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyStoreSynchronizeOneLevel(CExtPropertyItem * pPropertyItem=0x0470ccc0, CExtPropertyItem * pParentItem=0x045fe758) Line 6629 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyStoreSynchronizeOneLevel(CExtPropertyItem * pPropertyItem=0x045fe758, CExtPropertyItem * pParentItem=0x00000000) Line 6629 + 0x1a bytes    C++
    ProfUIS281md.dll!CExtPropertyGridWnd::PropertyStoreSynchronizeAll() Line 6501 + 0x18 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridCtrl::PropertyStoreSynchronize() Line 9417 + 0x12 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridCtrl::PropertyStoreSet(CExtPropertyStore * pPS=0x045fe758) Line 9444 + 0x12 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridComboBoxBar::_SynchronizeCurSel() Line 7759 + 0x16 bytes    C++
    ProfUIS281md.dll!CExtPropertyGridComboBoxBar::PropertyStoreInsert(CExtPropertyStore * pPropertyStore=0x045fe758, int nPos=0) Line 7684 + 0x12 bytes    C++
    GuiMdi.exe!CArchivePropertyCtrl::ShowArchive(const CArchivePropertyCtrl::PropertiesInfo & pi={...}) Line 230 + 0x18 bytes    C++

Yes, and we can provide you with the latest stable version 2.83. You can download it from our ftp server. Send us a request for details by email.

Will this change be incorporated in future versions of prof-uis?

Hallo,
I Have a class derived from CExtPropertyGridCtrl as follows:
class DataEntryGrid : public CExtPPVW < CExtPropertyGridCtrl >
I also have derived classes for the cells of the property grid.

I dynamically attach property stores on it with properties I create on runtime depending on the type of data I have.
Basically I would like to enable or disable properties during runtime depending on the values of other properties the user changes.

I would like to know if there is a way to disable a property so that it appears grayed and the user cannot enter any data.
Thanks in advance.

Thank you very much.
All this was most helpful.

The CExtPropertyGridCtrl class does not support print/preview. The CExtPPVW < CExtPropertyGridCtrl > template based class does. You should simply remove the CExtPPVW template from declaration of the property grid control in your project.

Thank you for your quick responce.
I have one more question.
The CExtPropertyGridCtrl also has the print and print preview buttons on it. Because it seems rather confusing for the user, is there a way to hide them or disable them?

1.
Create CExtGridWnd with default styles.
Modify styles SiwModifyStyle(__EGBS_GRIDLINES | __EGBS_SFM_FULL_ROWS | __EGBS_MULTI_AREA_SELECTION);
Try select some rows with SHIFT key - row selected but not redraw.
If I add SiwModifyStyle(__ESIS_STH_PIXEL|__ESIS_STV_PIXEL) the selection redraw successfully.
Why ?

2.
Create CExtGridWnd with styles:
SiwModifyStyleEx(__EGBS_EX_HVI_HIGHLIGHT_ROWS|__EGBS_EX_HVI_EVENT_CELLS|__EGBS_EX_HVI_HIGHLIGHT_CELL);
There are all ok - hovered row highlights successfully.
Set to all cells BackColorSet(CExtGridCell::__ECS_NORMAL, SomeColorRef);
Highlights only one hovered cell.
Why ?

We analyzed your request in more details and found that both ways are enough close to each other. A new version of CExtGridCell::e_cell_state_t specifies a greater number of supported color types:

      enum e_cell_state_t
      {
            __ECS_ALL                                 = 0, // color in any state
            __ECS_NORMAL                                    = 1, // normal, not hovered, not selected, not highlighted
            __ECS_SELECTED                            = 2, // selected
            __ECS_HOVERED                             = 3, // hovered
            // next added in 2.83
            __ECS_HIGHLIGHT_PRESSING                        = 4, // pressed
            __ECS_HIGHLIGHT_BY_FOCUS                        = 5, // in the same row or column with focused
            __ECS_HIGHLIGHT_BY_SELECTION              = 6, // in the same row or column with selected
            __ECS_HIGHLIGHT_BY_HOVER                        = 7, // in the same row or column with hovered
      };

I’d prefer second way.
I think what changing cell’s background color in __ECS_NORMAL state must not influence to full row highlighting.

The scrolling strategy style should be applied to the grid window at least in one of directions: horizontal or vertical. This is really required by the current implementation of the grid windows.

If the background color is specified to some grid cell, then it really ignores highlighting. There are two improvements can be done in the grid window:

1) We can add support for additional cell colors that can be used during highlighting. Currently only normal, hover, selected and single persistent colors are supported.

2) We can make highlighted cells ignore their preferred colors.

We think first case is better, but which of them would you prefer?

How can I get the rects of a cell in a ExtReportGridWnd given the
CExtReportGridColumn and CExtReportGridItem of the cell?

Thanks, Dave

Hi,

our application has a docked view containing a tree control that host various objects and view to reports, a bit like in Visual Studio.

The issue we face is:

On the toolbar (a CExtToolControlBar), click on pixel left or right of a separator -> the toolbar is inactive.

The issue I clearly face here is that my view looses the focus -> the update mechanism is broken.

I try to restore it by setting the active view. The issue I now is that my toolbar is partially activated either the buttons linked to the tree or the ones linked to the view.

Any idea or suggestion ?

I’m using the 2.7.0 version of the toolkit.

We set a breakpoint to case WM_SETFOCUS in CExtControlBar::WindowProc(). So, we can catch the focus setting event on the toolbar. We run the SDI sample and set focus on the editor inside the Resizable Bar 0 bar. If the main frame window is active, then dragging start event of the toolbar will never make the toolbar focused. If the frame window is inactive and you are starting to drag-n-drop the toolbar window through its gripper or any separator, then the toolbar may become focused but this is not exactly related to the problem described in your message. Fortunately, the MthOutput sample application allowed us to reproduce this issue successfully. We found a situation when the code of the CExtControlBar class can really set focus to itself without analyzing whether the bar is a resizable panel bar or a toolbar. The problem can be solved in two steps:

1) Update the source code of the following overloaded version of the CExtControlBar::stat_QueryFocusChangingEnabled method:

bool CExtControlBar::stat_QueryFocusChangingEnabled(
      HWND hWndNotifyTarget,
      CWnd * pWndQueryOwner,
      HWND hWndNewFocusOwner
      )
{
      ASSERT( hWndNotifyTarget != NULL && ::IsWindow( hWndNotifyTarget ) );
      ASSERT_VALID( pWndQueryOwner );
      ASSERT( pWndQueryOwner->GetSafeHwnd() != NULL );
      ASSERT( hWndNewFocusOwner != NULL && ::IsWindow( hWndNewFocusOwner ) );
CExtControlBar * pBar = DYNAMIC_DOWNCAST( CExtControlBar, pWndQueryOwner );
      if(         pBar != NULL
            &&    pBar->IsFixedMode()
            )
            return false;
QueryFocusChangingEnabled_t _QFCE( pWndQueryOwner, hWndNewFocusOwner );
      ::SendMessage( hWndNotifyTarget, g_nMsgQueryFocusChangingEnabled, _QFCE, 0 );
      return _QFCE.m_bFocusChangingEnabled;
}

. . .
            } // if( ! bEnableStartDragging )
      } // if( sizeWaitMouseMove.cx > 0 && sizeWaitMouseMove.cy > 0 )
      //ASSERT( CExtMouseCaptureSink::GetCapture() == hWndOwn );
      CExtMouseCaptureSink::SetCapture( hWndOwn );
      _SetCursor( point );
      m_bDragDetecting = false;

      ASSERT( g_DragStateOld.IsEmpty() );
      ASSERT( g_DragStateNew.IsEmpty() );
      g_DragStateOld.ExtBarSrcSet( this );
. . .

the call stack is

>    FiREGrids.dll!FReportView::OnKillFocus(CWnd * pWnd=0x04b8ea68) Line 2400    C++
    mfc80d.dll!CWnd::OnWndMsg(unsigned int message=8, unsigned int wParam=1183186, long lParam=0, long * pResult=0x0012e230) Line 2079    C++
    mfc80d.dll!CWnd::WindowProc(unsigned int message=8, unsigned int wParam=1183186, long lParam=0) Line 1741 + 0x20 bytes    C++
    og801asd.dll!CGXGridView::WindowProc(unsigned int message=8, unsigned int wParam=1183186, long lParam=0) Line 333    C++
    FiREGrids.dll!GTBContentBasedView::WindowProc(unsigned int message=8, unsigned int wParam=1183186, long lParam=0) Line 347 + 0x14 bytes    C++
    mfc80d.dll!AfxCallWndProc(CWnd * pWnd=0x085f1818, HWND__ * hWnd=0x00401008, unsigned int nMsg=8, unsigned int wParam=1183186, long lParam=0) Line 240 + 0x1c bytes    C++
    mfc80d.dll!AfxWndProc(HWND__ * hWnd=0x00401008, unsigned int nMsg=8, unsigned int wParam=1183186, long lParam=0) Line 389    C++
    mfc80d.dll!AfxWndProcBase(HWND__ * hWnd=0x00401008, unsigned int nMsg=8, unsigned int wParam=1183186, long lParam=0) Line 411 + 0x15 bytes    C++
    user32.dll!GetDC() + 0x6d bytes    
    [Frames below may be incorrect and/or missing, no symbols loaded for user32.dll]    
    user32.dll!GetDC() + 0x14f bytes    
    user32.dll!DefWindowProcW() + 0x184 bytes    
    user32.dll!DefWindowProcW() + 0x1d0 bytes    
    ntdll.dll!_KiUserCallbackDispatcher@12() + 0x13 bytes    
    user32.dll!SetFocus() + 0xc bytes    
    ProfUIS270nd.dll!CExtControlBar::_DraggingStart(const CPoint & point={...}, const CPoint & pointOffset={...}, CSize sizeWaitMouseMove={...}) Line 12176    C++
    ProfUIS270nd.dll!CExtControlBar::OnLButtonDown(unsigned int nFlags=1, CPoint point={...}) Line 9960 + 0x2d bytes    C++
    ProfUIS270nd.dll!CExtToolControlBar::OnLButtonDown(unsigned int nFlags=1, CPoint point={...}) Line 10789    C++
    mfc80d.dll!CWnd::OnWndMsg(unsigned int message=513, unsigned int wParam=1, long lParam=655768, long * pResult=0x0012e8e8) Line 2169    C++
    mfc80d.dll!CWnd::WindowProc(unsigned int message=513, unsigned int wParam=1, long lParam=655768) Line 1741 + 0x20 bytes    C++
    mfc80d.dll!CControlBar::WindowProc(unsigned int nMsg=513, unsigned int wParam=1, long lParam=655768) Line 504 + 0x14 bytes    C++
    ProfUIS270nd.dll!CExtControlBar::WindowProc(unsigned int message=513, unsigned int wParam=1, long lParam=655768) Line 8536    C++
    ProfUIS270nd.dll!CExtToolControlBar::WindowProc(unsigned int message=513, unsigned int wParam=1, long lParam=655768) Line 12839    C++
    mfc80d.dll!AfxCallWndProc(CWnd * pWnd=0x04b8ea68, HWND__ * hWnd=0x00120dd2, unsigned int nMsg=513, unsigned int wParam=1, long lParam=655768) Line 240 + 0x1c bytes    C++
    mfc80d.dll!AfxWndProc(HWND__ * hWnd=0x00120dd2, unsigned int nMsg=513, unsigned int wParam=1, long lParam=655768) Line 389    C++
    mfc80d.dll!AfxWndProcBase(HWND__ * hWnd=0x00120dd2, unsigned int nMsg=513, unsigned int wParam=1, long lParam=655768) Line 411 + 0x15 bytes    C++
    user32.dll!GetDC() + 0x6d bytes    
    user32.dll!GetDC() + 0x14f bytes    
    user32.dll!GetWindowLongW() + 0x127 bytes    
    user32.dll!DispatchMessageA() + 0xf bytes    
    mfc80d.dll!AfxInternalPumpMessage() Line 183    C++
    mfc80d.dll!CWinThread::PumpMessage() Line 896    C++
    [Managed to Native Transition]    
    FRC.exe!FFiREApp::PumpMessage() Line 748 + 0xb bytes    C++
    [Native to Managed Transition]    
    mfc80d.dll!CWinThread::Run() Line 625 + 0xd bytes    C++
    mfc80d.dll!CWinApp::Run() Line 894    C++
    mfc80d.dll!AfxWinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00151f10, int nCmdShow=5) Line 47 + 0xd bytes    C++
    FRC.exe!WinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00151f10, int nCmdShow=5) Line 33    C++
    FRC.exe!__tmainCRTStartup() Line 589 + 0x35 bytes    C
    FRC.exe!WinMainCRTStartup() Line 414    C
    mfc80d.dll!CWinThread::Run() Line 625 + 0xd bytes    C++
    mfc80d.dll!CWinApp::Run() Line 894    C++
    mfc80d.dll!AfxWinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00151f10, int nCmdShow=5) Line 47 + 0xd bytes    C++
    FRC.exe!WinMain(HINSTANCE__ * hInstance=0x00400000, HINSTANCE__ * hPrevInstance=0x00000000, char * lpCmdLine=0x00151f10, int nCmdShow=5) Line 33    C++
    FRC.exe!__tmainCRTStartup() Line 589 + 0x35 bytes    C
    FRC.exe!WinMainCRTStartup() Line 414    C
    ntdll.dll!_RtlFreeHeapSlowly@12() + 0x207 bytes    
    ntdll.dll!_RtlFreeHeapSlowly@12() + 0x207 bytes    
    ntdll.dll!_LdrpGetProcedureAddress@20() + 0x136 bytes    
    ntdll.dll!_RtlAllocateHeap@12() + 0x117 bytes    

as you can read the Toolbar enters in a ::_DraggingStart(...) function -> it seems that we don’t exit properly

The window that kills the focus is

+        pWnd    0x04b8ea68 {CExtToolControlBar hWnd=0x00120dd2}    CWnd *

What can I do ?

Hello,

I want to insert a toplevel popup menu into any existing menu. Using a MFC-Application without Prof-UIS the code:
CMenu* pMenu    = AfxGetMainWnd()->GetMenu();
if (pMenu != NULL) {
CMenu    cmInsert;
                if (cmInsert.LoadMenu(IDR_INSERT_4_DB)) {
/*
                CMenu*    pSubMenu = cmInsert.GetSubMenu(0);
                UINT    nFlags = MF_BYPOSITION | MF_POPUP;
                nFlags = MF_BYPOSITION;
                nFlags = MF_POPUP;
                nFlags = MF_BYPOSITION | MF_POPUP;
                pMenu->InsertMenu(1, nFlags, (UINT_PTR)pSubMenu->m_hMenu);
*/
                CMenu* pPopupMenu = cmInsert.GetSubMenu(0);
                // get its string - *ˆ&) Windows can’t figure it out for itself
                CString strMenuItem;
                cmInsert.GetMenuString(0, strMenuItem, MF_BYPOSITION);

                // Add it
                VERIFY(pMenu->InsertMenu(1, MF_BYPOSITION | MF_POPUP,
                    (UINT)pPopupMenu->GetSafeHmenu(), strMenuItem));
                // remove from the other menu!
                cmInsert.RemoveMenu(0, MF_BYPOSITION);


                DrawMenuBar();
//                    pMenu->InsertMenu(1, MF_BYPOSITION | MF_POPUP, (UINT_PTR)cmInsert.m_hMenu);
                }
            }
        }

The CExtMenuControlBar class kills main frame’s menus and completely monitors menu changing in MDI main frames. It keeps current the main frame’s menu handle internally and uses it for building its toolbar buttons. So the top menu level is ab array of toolbar buttons in the menu bar. You can override the CExtMenuControlBar::_UpdateMenuBar() internal virtual method which builds toolbar buttons. Your method should be similar to the original one except it should insert the additional top level buttons like you need. You should invoke the following code from outside the menu bar to make it rebuild and update its content:

CExtMenuControlBar * pBar = . . .
      pBar->UpdateMenuBar();
      pBar->GetParentFrame()->RecalcLayout();

Hello Group and Support,

I’ve installed version Prof-UIS 1.82 on to my Vista machine with Visual Studio 2008 installed. The installation seemed to go well. However the Integration Wizard fails. I select "Add Prof-UIS paths to Visual environment variables for Win32 platform", Add wizard to Visual studio and the integration wizard fails on the environment variables and shows a strange error, "-Remove Prof-UIS paths from Visual Studio environment variables for Win32 platform". However I selected _ADD_ variables. The second failure is the VS "New Project". I select a new project using Prof-UI and state the path and project name click OK and nothing happens.

What have I not done to cause these failures?

The report:

/*******************************************************************/
    REPORT FILE [1-27-2008, 20:28]
/*******************************************************************/

Remove Prof-UIS paths from Visual Studio environment variables for Win32 platform - Failed.

Install Prof-UIS Application Wizard to Visual Studio - Succeeded.

TIA

Thanks for the reply. Here are some more details:

OS:
Windows Vista Ultimate 32 bit

VS 2008 Pro:
* Installed using all of its default parameters and in its default directory (c:\Program Files\Microsoft Visual Studio 8).
* The VS 2008 Pro is taken from the MSDN library.

Integration Wizard:
* Vista Ultimate 32 bit.
* Trying to add support to WS 2008 for 32 bit build.
* Fails on creating environment variables. The check box is there and selected. The error message is as if I was trying to REMOVE the environment variables.
* 32 Bit build fails

Creating a new Prof-UI project from VS 2008
* The project option exists on the new project for VC++
* When OK is selected, the wizard never appears so I cannot step through any of the pages.

Other notes:
I tried to uninstall 1.82 and clean the directory and reinstall it.

Please let me know if there are any other parameters you would like to see.

Monte--

Please provide some more details about the problem. Which version of Windows Vista, Win32 or x64? Which language?
If Visual Studio 2008 is installed into the default location and if its installation path contains some no-English characters?
Does the Application Wizard work correctly in any other cases? Will it work if you go through its pages?

Hi,

I need to implement a tree grid with 100,000 rows - is it possible?

Thanks,
Ron.

Hello,

I have CExtGridWnd object with two columns. I would like to set second column width to occupy all free space available in CExtGridWnd window.

Thank you.

Hello.

I want to make width of here wide.
http://www.yukai.jp/~ifreeta/20080125/image05.jpg

Please teach a way.
Thanks,

Hello.

I do not have any problem.
I was not able to understand English answers well.
I decide to use the thing of new Version.
Thank you.

We do not support old versions. Do you have any strong reason not to switch to to a newer version ?

I use Prof-UIS2.70.
However, the application does not work well ????

We already fixed this issue. You should use a newer version than 2.70.

Hello.

Please answer.

Hello.

>Could you put the source code which produces this screen shot into our sample application and send it to us?
In the source which I sent last time, will "Debug" be impossible?


http://www.yukai.jp/~ifreeta/20080219/RibbonBarTestA.lzh
I incorporated it in RibbonSample. (--;
Please answer me.

Could you put the source code which produces this screen shot into our sample application and send it to us?

We cannot reproduce similar painting effects. Could you ensure both the main frame window and un-painted container window are created with the WS_CLIPSIBLINGS|WS_CLIPCHILDREN standard window styles?

Hello.

Are you investigating the following matter?
http://www.yukai.jp/~ifreeta/20080214/image01.jpg

I want to display it with a Combo form
The application becomes the text box.

Thanks,

Hello.

>How to reproduce this incorrect painting effect with our sample applications?
This problem seems to occur only at the time of theme 2003.

It is a reproduction method.
1) You start application in this state.
http://www.yukai.jp/~ifreeta/20080216/image01.jpg

2) You widen SampleBar
http://www.yukai.jp/~ifreeta/20080216/image02.jpg

3) A background is not drawn.
http://www.yukai.jp/~ifreeta/20080216/image03.jpg
http://www.yukai.jp/~ifreeta/20080216/image04.jpg

If this issue is in Prof-UIS, then it’s in any tab page container and not only in the flat tab page container. How to reproduce this incorrect painting effect with our sample applications?

Hello.

I sent an email.

2) Then please examine the other malfunction
An afterimage remains with theme 2003.
Please examine it.
http://www.yukai.jp/~ifreeta/20080215/image01.jpg

Could you please reproduce this problem with our RibbonBar sample and send it to us?

Hello.

http://www.yukai.jp/~ifreeta/20080214/image01.jpg
A frame is not displayed.
It is not displayed with a combo form
Please teach it

Thanks,

You should add the following two files to your project:

// in .H file

class CYourTextFieldButton : public CExtBarTextFieldButton
{
public:
      DECLARE_DYNCREATE( CYourTextFieldButton );
      CYourTextFieldButton(
            bool bComboField = false,
            INT nTextFieldWidth = __EXT_MENU_DEF_INPLACE_EDIT_WIDTH,
            CExtToolControlBar * pBar = NULL,
            UINT nCmdID = ID_SEPARATOR,
            UINT nStyle = 0
            )
            : CExtBarTextFieldButton(
                  bComboField,
                  nTextFieldWidth,
                  pBar,
                  nCmdID,
                  nStyle
                  )
      {
      }
      virtual CSize CalculateLayout(
            CDC & dc,
            CSize sizePreCalc,
            BOOL bHorz
            )
      {
            ASSERT_VALID( this );
            CSize _size = CExtBarTextFieldButton::CalculateLayout( dc, sizePreCalc, bHorz );
            _size.cy += 10; // make it 10 pixels larger in height
      }
 };

class CYourTextFieldNode : public CExtRibbonNode
{
public:
      DECLARE_SERIAL( CYourTextFieldNode );
      CYourTextFieldNode(
            UINT nCmdIdBasic = 0L,
            UINT nCmdIdEffective = 0L,
            CExtRibbonNode * pParentNode = NULL,
            DWORD dwFlags = 0L,
            __EXT_MFC_SAFE_LPCTSTR strTextInToolbar = NULL,
            __EXT_MFC_SAFE_LPCTSTR strTextInMenu = NULL,
            __EXT_MFC_SAFE_LPCTSTR strTextUser = NULL,
            LPARAM lParam = 0L,
            CExtCmdIcon * pIconCustomized = NULL,
            INT nTextFieldWidth = 100,
            INT nDropDownWidth = -2, // (-1) - auto calc, (-2) - same as button area
            INT nDropDownHeightMax = 250
            );
      CExtRibbonNode(
            UINT nCmdIdBasic = 0L,
            UINT nCmdIdEffective = 0L,
            CExtRibbonNode * pParentNode = NULL,
            DWORD dwFlags = 0L,
            __EXT_MFC_SAFE_LPCTSTR strTextInToolbar = NULL,
            __EXT_MFC_SAFE_LPCTSTR strTextInMenu = NULL,
            __EXT_MFC_SAFE_LPCTSTR strTextUser = NULL,
            LPARAM lParam = 0L,
            CExtCmdIcon * pIconCustomized = NULL,
            INT nTextFieldWidth = 100,
            INT nDropDownWidth = -2, // (-1) - auto calc, (-2) - same as button area
            INT nDropDownHeightMax = 250
            );
      virtual CRuntimeClass * _OnRibbonGetButtonRTC()
      {
            ASSERT_VALID( this );
            return ( RUNTIME_CLASS( CYourTextFieldButton ) );
      }
      virtual CExtBarButton * OnRibbonCreateBarButton(
            CExtRibbonPage * pBar,
            CExtBarButton * pParentTBB = NULL
            )
      {
            CYourTextFieldButton * pTextFieldTBB  =
                  STATIC_DOWNCAST(
                        CYourTextFieldButton,
                        CExtRibbonNode::OnRibbonCreateBarButton( pBar, pParentTBB )
                        );
            pTextFieldTBB->m_nDropDownWidth = DropDownWidthGet();
            pTextFieldTBB->m_nDropDownHeightMax = DropDownHeightMaxGet();
            pTextFieldTBB->m_bTextFieldIsNotEditable = ( GetFlags() & __ECTN_TBB_TF_NE ) ? true : false;
            return pTextFieldTBB;
      }
};

// in .CPP file

IMPLEMENT_DYNCREATE( CYourTextFieldButton, CExtBarTextFieldButton );
IMPLEMENT _SERIAL( CYourTextFieldNode, CExtRibbonNode );

Hello.

Please answer it

Hello.

I do not understand ways of the descriptions well.
I ask for your sample code.

Thanks

It’s possible to specify the width of text or combo field. The height is measured automatically. If you need some custom height, you should implement a text field button class like we advised on our previous answer and implement the CExtBarButton::CalculateLayout() virtual method in it. Your method should invoke parent class method and then increase the CSize::cy height value before returning the CSize object.

Can the PageRemove() method be used without selecting the previous page in a tab strip in the class CExtTabPageContainerWnd . Because the PageRemoveAll() method does not work. Please treat it as urgent!

Hello.

In RibbonBar, I want to display such an image.
http://www.yukai.jp/~ifreeta/20080125/image03.jpg

Please teach a way.
Thanks,

Hello.

I want to move an image a little in the arrow direction.
Please teach a way.

http://www.yukai.jp/~ifreeta/20080125/image01.jpg

Thanks,

Dear Support,

I found some problems in our multiline grid cell. It can be reproduced in your ProfUIS_Controls sample. Go to Grid page and then to Text column. Go into edit mode in one of the multiline cells and place the cursor to the very end of the first line. If you press Delete key here, you can see a square kind of character appearing between the texts "Cellx Line1" and "Cellx Line2". I think it is connected to how VK_DELETE is handled in the in-place editor’s message loop in CExtGridWnd::OnGbwBeginEdit.

Could you please check this issue?
Thank you!

Dear Support,

We get repeat complains from our customers that when a cell is read-only it is impossible to read it - the color scheme is too light.
The theme we use is CExtPaintManagerOffice2007_Blue and the problem is when we set the attribute __EGCS_READ_ONLY

1. I think that this is a problem in the skin that should be modified.
2. If not, can you please explain us how to change this specific color so that it will be readable.

Thanks,
Ron.

You can download the latest source code from our ftp server. Please contact us for details via email.

Yes - this how it should look...
Can you please send me the updated version? I need to release a version ASAP.

Thanks,
Ron.

Here is what we have now:



Please let us know if it is what you mean?

My problem is that they are not even gray... when I add
pCellString->ModifyStyle(__EGCS_READ_ONLY);
The cell looks exactly the same as a editable cell, only it is not editable.
In version 2.72 the gray was too light, and in 2.82 there gray is black.

Again, I am in CExtPaintManagerOffice2007_Blue - please check it with it, not apple not Obsidian.

We followed your advice and here is the result:



But read-only cells look like disabled dialog items rather than grid cells. What do you think? We would prefer to leave them white with gray text.

Dear Support,

The problem is with grid cells - not with normal controls - grit controls with the read-only (__EGCS_READ_ONLY) looks the same as cells that are not read-only, and they should have a gray background like the controls.

Thanks,
Ron.

Here is the screen shot demonstrating the current versions of the read only combo box and edit controls in Office 2007 Obsidian theme:



Please let us know what should we change.

I’m using v2.81.
I have just had another issue reported, read only combo box using CExtPaintManagerOffice2007_Black is unreadable.
not sure if that’s changed in 2.82.

Hi,

I upgraded to 2.82, now, in CExtPaintManagerOffice2007_Blue read-only cells’ text is black like editable cells.
It is not as bad as before, because you can read them - but there is no indication that they are read-only...
Support - is this the way it should be?
Ian - what version are you using?

Regards,
Ron.

I also have had similar comments from my users (although I didn’t seem to get the same problem on my pc).

I added the following code:

#define RGB_CELL_TEXT RGB(0,0,75)

pCellString->ModifyStyle(__EGCS_READ_ONLY);
pCellString->TextColorSet(CExtGridCell::__ECS_NORMAL, RGB_CELL_TEXT);

but it would obviously be preferable if I didn’t have to.

If this has been sorted, please could you post the solution.
Thanks.

I am sending it again... let me know if you haven’t received it - I am sending it to support@prof-uis.com

We are sorry but have not yet received the screen shot.

Dear Support,

The Read-Only color color is not black, it’s very light blue.

I am sending you as screen-shot.

Regards,
Ron.