Forum

I  ran "RibbonBarMDI" example and recognized the following error:

When I removed some TabPage in RibbonPage_Home:



CExtRibbonNode * CMainFrame::_InitRibbonPage_Home()

{

CExtRibbonNodeTabPage * pRibbonNodeTabPage = new CExtRibbonNodeTabPage( 0L, NULL, _T("Home") );

    pRibbonNodeTabPage->CmdKeyTipSet( new CExtCustomizeCmdKeyTip( __EXT_MFC_SAFE_TCHAR( _T(’H’) ) ), false );

    pRibbonNodeTabPage->InsertNode( NULL, _InitRibbonNode_Home_Clipboard() );

    pRibbonNodeTabPage->InsertNode( NULL, _InitRibbonNode_Home_Font() );

    //pRibbonNodeTabPage->InsertNode( NULL, _InitRibbonNode_Home_Paragraph() );

    //pRibbonNodeTabPage->InsertNode( NULL, _InitRibbonNode_Home_Style() );

    //pRibbonNodeTabPage->InsertNode( NULL, _InitRibbonNode_Home_Find() );

    return pRibbonNodeTabPage;

}

If I click maximize button in main frame and then click restore button in main frame, I recognized the difference position on RibbonPage_Home ( you can see screenshots)

 

Please fix this error because my application has the above error  !

Thanks !

Thank you very much for reporting this issue. It is fixed. Here is a test application that demonstrates that the problem has gone:

http://www.prof-uis.com/download/forums/TestProblemReportedByDeveloperNCS.zip

Please request the source code update by email.

Dear sirs,

How do I know when a tabbed control bar (CExtDynTabControlBar) is pressed and selected?

Which event should I override to get this?

Thanks a lot.

Regards,

Chun Pong

You should handle the WM_WINDOWPOSCHANGED message in your CExtControlBar-derived class to catch any position change of the control bar. Here is how to determine whether the bar is selected in a tabbed bar group:

http://www.prof-uis.com/prof-uis/tech-support/general-forum/cextcontrolbar-focus-1295.aspx#61785

I just started replacing some of my CTabCtrls with CExtTabPageContainerWnds.  While I do think the page container functionality is more intuitive than the truely bizarre CTabCtrl (and underlying Windows Common control) behavior, I find that I really miss the borders offered by the Windows control.

I am aware that CExtTabPageContainerWnd is written from the ground up and is not related to CTabCtrl.  However, the bordres would really be nice.  Is it possible to display a border (around the child pages) similar to the CTabCtrl?  If so, how?  If not, can this be a feature request?

 

 

You can apply the WS_EX_STATICEDGE window style for your tab page container window.

m_wndTabPageContainer.ModifyStyleEx( 0, WS_EX_STATICEDGE );
 
UINT nSetWindowPosFlags =
            SWP_NOMOVE|SWP_NOSIZE
            |SWP_NOZORDER|SWP_NOOWNERZORDER
            |SWP_NOACTIVATE
            |SWP_FRAMECHANGED
            ;
m_wndTabPageContainer.SetWindowPos(NULL,0,0,0,0,nSetWindowPosFlags);  

You can see how it is done in the ProfUIS_Controls sample on the "Tab Containers" page when you click the "Show borders" check box.

The frame should be around the contained dialog/control and not the tab. This solution doe not work.

Please look at all modern tabs - the contained contained window is somehow linked to the tab control.

Would you send us two screen shots :

1) Some modern tabs without any problems.

2) Our tabs in your application that causes problems.

Here are two samples:

I can send yo more if you want...

 

Hi !

I’m using Prof-uis v.2.83 for MFC and VC++ 2005 and my application created like RibbonBar MDI example but using Doc/View architecture. My application consist of a main frame and multi child frame ( child frame for each document ). When i modified document in a child frame and then click [x] button in main frame, a messagebox will be appeared to ask saving the changes you made to the document.

In version 2.82 everything is good but i build in version 2.83 when i click [x] button in main frame a messagebox  still appeared but ribbonbar is disappear.

If i click "cancel" button to return main frame, some icons, some tab ribbon, file button are disappear.

 

And then if I click a tab ribbon or click maximize button ...., everything is just normal. I don’t know what happens. Please help me fix it.

I’ve sent an email to support email. Please reply to me (email: bonmat179@gmail.com) as soon as possible ! Thanks alot  !

We replied you by email.

Is there any way to left justify the text in a CExtHyperlinkButton control?

The hyperlink is based on a button common control. So it uses the button’s window styles for text alignment: BS_LEFT, BS_CENTER, BS_RIGHT, BS_TOP, BS_VCENTER and BS_BOTTOM.

Hello.

I make a group node display or non-display by pushing the ID_EDIT_CLEAR button

http://ifreeta.dee.cc/20080925/RibbonBar.lzh

In CExtRibboPage, the bar does not flicker in particular.

In CExtRibbonBar, the following point flickers.

 

Please teach improvement plan.

 

Here is the modified version of your project:

http://www.prof-uis.com/download/forums/RibbonBar_for_tera_t-fixed000.zip

First of all, we added a MY_WM_DELAYED_UI_INIT message and a CMainFrame::OnMyDelayedUiInit() handler method for delayed initialization of the dialog, which resolves the problems with skinned non-client area of the main frame window. Second, we invoked the CWnd::RedrawWindow() and CExtPaintManager::stat_PassPaintMessages() APIs in the ID_EDIT_CLEAR() of the CMainFrame::OnCmdMsg() virtual method for avoiding re-painting effects related to the scroll bar control inside gallery control. We suppose that was the flicker effect explained in your message.

 

Thank you for an answer.

However, the place where this focus is flickers.

Please teach a good method.

Is it difficult?.

 

Could you please explain us some more details about this flicker effect? Typically flicker effects are generated by more than one painting of the same screen areas. For instance, first time screen area is painted with some color and next time some control or its part appear on the screen. We didn’t see such effects in the ribbon.

Hello.

This sample program flickers.

If there is a good method, please teach it.

Please explain us details about flickering. We do not see anything painted and then over-painted. We do not see flicker effects. Maybe you mean something else what painted incorrectly in your point of view?

Hello.

http://ifreeta.dee.cc/20080929/result.avi

A focus flickers with my PC in this way.

Please teach a good method.

 

Hi,

I am handling the button pressed events of some of our grids. Currently, the only way to do it is to override the cell. The problem is that we need this to be done at the grid level and not the cell level. I think that this is a very simple change in the code, that could benefit a lotof users.

All that there needs to be done is to add a virtual OnButtonPressed function to theCExtGridWnd, and call it every place you call pCell->OnButtonPressed.

What do you say? will you be able to squeeze this into 2.84?

Thanks,

Ron.

The CExtGridCell::OnButtonPressed() virtual method invocations are redirected to the CExtGridWnd::OnGridCellButtonPressed() virtual method.

Dear ProfUIS-Team,



now, after some time has gone since my bug report (see comm. from 2008/02 below) I’d like to ask you if there is any solution available to this problem. Please give me a short outlook on how to proceed.

By the way, could you please tell me (approximately) when the next version is planned to be released? Thanks in advance!



Best regards,

Martin









##############   comm. 2008/02   #####################



Dear ProfUIS-Team,



thank you for your efforts! Because the persistency feature is rather important for our application we internally came to the agreement to keep version 2.80 alive until an appropriate solution is found for this problem. Please send us a short note to confirm the fix.



One more question: is it possible to prevent the main window from being included into the serialization process (I/O)? And what would be the appropriate way to deal with this?



Best regards,



Martin







Prof-UIS Technical Support Team schrieb:

<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->

Dear Martin,<o:p></o:p>

<o:p> </o:p>

We confirm that the problem your reported exists. It occurs in some particular situations when control bars are organized in some complex layout. It never occurs when control bars are organized in some simple layout, for instance, if all the control bars are docked vertically on left and each is single in its column of bars. All the bars in this case can be hidden or visible. The most important thing is that this simple layout does not have deep level nested splitter bar containers. This problem does not occur with dynamic resizable control bars (see SDI_DynamicBars sample application) because all the just allocated bars are organized in some simple layout like discussed above and state re-loading typically means re-allocation of all the bars because number of bars in different states can be different. We need additional time to find some appropriate solution.<o:p></o:p>

<o:p> </o:p>

Please do not hesitate to contact us if you have any questions.<o:p></o:p>

 <o:p></o:p>

Best regards, 

Technical Support Team<o:p></o:p>

 <o:p></o:p>

FOSS Software, Inc.

Phones: (603) 894 6425

             (603) 894 6427

Email:   support@prof-uis.com<o:p></o:p>

<o:p> </o:p>

Sent: Thursday, February 21, 2008 6:10 PM

To: support@prof-uis.com

Subject: Re: Serialization bug: loading an archive file<o:p></o:p>

<o:p> </o:p>

Dear ProfUIS-Team,



just for my info: could you reproduce the described behaviour? Thanks in advance.



Martin



################################ First message #######################################



Dear ProfUIS-Team,



sorry for your inconvenience because of my holey description of the problem. ;-)



As an attachment you’ll find three archives that are used in the following procedure.



First of all, I have tried to load your archive_01.FPX and it works like shown in the image you sent me. Loading it immediately after the first load works without problems, too.



But on a second glance, I found out how to disturb the correct behaviour of loading that archive by performing the following steps:



1. Start Application from scratch after preceding deletion of archive_00.FPX (is ok, uses defaults)

2. Load archive_01.FPX (is ok, same as shown in your image file)

3. Load archive_02.FPX (is ok)

4. Load archive_03.FPX (is ok, should look similar to correct.jpg)

5. Load archive_03.FPX immediatly once more (is not ok, should look similar to INcorrect.jpg)

6. Load archive_01.FPX second time (is not ok, compared with original PNG)



It’s obvious that something in the constellation of archive_03.FPX confuses the loading of archive_01.FPX. Please note that step 5. is not necessary at all to disarrange archive_01.FPX. In contrast, replaying step 3. several times never leads to a bad result.



Would you please try to follow this procedure step by step using the attached archive files?



Best regards,



Martin





Prof-UIS Technical Support Team schrieb: <o:p></o:p>

Dear Martin,<o:p></o:p>

 <o:p></o:p>

We compiled and run your application successfully. We found nothing wrong. The archive_01.FPX state file restores the main frame maximized state when others are restoring in the normal state. The single monitor computer was used in the test and monitor resolution was enough high - 1440x1050. All the state files do not contain description of floating bars.<o:p></o:p>

 <o:p></o:p>

We tried to save/load different bar layouts using your test version of our sample application and everything was OK independently from the number of floating bars. Could you please describe some step by step actions which we should perform to reproduce the problem.<o:p></o:p>

 <o:p></o:p>

Here is attached the ZIP file with the control state data file and PNG screen shot made on 1440x1050 single monitor desktop describing what you should get when restore the control bar state from the file saved on our computer. Please note, if you will restore our state file on a computer with smaller resolution desktop, then Prof-UIS will change positions of floating bars which are outside the desktop to make them visible.<o:p></o:p>

 <o:p></o:p>

Please do not hesitate to contact us if you have any questions.<o:p></o:p>

 <o:p></o:p>

Best regards, 

Technical Support Team<o:p></o:p>

 <o:p></o:p>

FOSS Software, Inc.

Phones: (603) 894 6425

             (603) 894 6427

Email:   support@prof-uis.com<o:p></o:p>

 <o:p></o:p>

Sent: Friday, February 15, 2008 8:12 PM

To: support@prof-uis.com

Subject: Serialization bug: loading an archive file<o:p></o:p>

 <o:p></o:p>

Dear ProfUIS-Team,



there appears to be a bug with floating window persistence if loading an archive file. We could reproduce the buggy behaviour after having implemented the archive load/save features in your ProfStudio sample application. I’ll immediately send you the corresponding souce code attached to an email for support@prof-uis.com.



The inconsistency especially appears when loading the file archive_01.FPX not only once but twice.



Best regards,



Martin <o:p></o:p>

<o:p> </o:p>

It looks like we fixed the serialization issues. Could you drop us an e-mail to the support mail box at this web site so we will provide you with the source code update.

I have a text field attached to a toolbar that does validation when the enter key is pressed.  After the enter key is pressed validation is performed on the text in the text field and if the data is bad then a message box describing the error is shown.  Now when the text field is hidden and accessed through a popup menu launched by the chevron on the toolbar an assert and then exception are thrown if the user enters bad data in the text field and presses the enter key.  I’m assuming the assert/exception are happening because the menu has been prematurely destroyed.  Is there any way to keep the popup menu from being destroyed while I display an error message.

 

Here is part of the call stack that shows the assert/exception location.

CExtPopupMenuWnd::MENUITEMDATA & CExtPopupMenuWnd::ItemGetInfo( INT nPos )
{
ASSERT_VALID(
INT nCountOfItems = ItemGetCount();
 
{
ASSERT( FALSE );                               <=- Assert being fired off
AfxThrowNotSupportedException();
}
 
}this );    if( nPos < 0 || nPos >= nCountOfItems )    return _GetItemRef( nPos );
 
void
{
ASSERT_VALID(
 
 
m_bCanceling =
 
{
 
m_pWndParentMenu->_CancelingSet();
}
 
&& ItemGetInfo( m_nCurIndex ).IsPopup()
)                                               <=- Call stack position
{
CExtPopupMenuWnd * pPopup = ItemGetInfo( m_nCurIndex ).GetPopup();
 
pPopup->_CancelingSet();
}
} CExtPopupMenuWnd::_CancelingSet()this );    if( m_bCanceling )        return;true;    if( m_pWndParentMenu != NULL )        if( ! m_pWndParentMenu->_CancelingGet() )    if( m_nCurIndex >= 0        if( ! pPopup->_CancelingGet() )

 
 
#if _MFC_VER < 0x700
void CExtPopupMenuWnd::OnActivateApp(BOOL bActive, HTASK hTask) 
#else
void CExtPopupMenuWnd::OnActivateApp(BOOL bActive, DWORD hTask) 
#endif
{
ASSERT_VALID(
bActive;
hTask;
_CancelingSet();                                    <=- Calling stack position
_OnCancelMode();
}this );

 

 

Kevin Eshbach

Hi



How can I disable the pulldown menu of the linewidth button in the DRAWCLI sample application? It pops up when I click on it although the button itself is disabled (i.e. when no object is selected).



Thanks - Peter

http://www.prof-uis.com/prof-uis/tech-support/support-forum/cextgridcellcombobox-color-bug-in-283-61168.aspx#@lt;/p>

This behavior is provided by implementation of the CExtGridCell::OnQueryTextColor virtual method in the CExtGridCellComboBox class:

COLORREF CExtGridCellComboBox::OnQueryTextColor(
      const CExtGridWnd & wndGrid,
      CDC & dc,
      LONG nVisibleColNo,
      LONG nVisibleRowNo,
      LONG nColNo,
      LONG nRowNo,
      INT nColType,
      INT nRowType,
      DWORD dwAreaFlags,
      DWORD dwHelperPaintFlags
      ) const
{
      ASSERT_VALID( this );
COLORREF clrText = CExtGridCellString::OnQueryTextColor( wndGrid, dc, nVisibleColNo, nVisibleRowNo, nColNo, nRowNo, nColType, nRowType, dwAreaFlags, dwHelperPaintFlags );
      if( clrText != COLORREF(-1L) )
            return clrText;
      if( (dwHelperPaintFlags&__EGCPF_PRINTING_TARGET_MASK) != 0 )
            return COLORREF(-1L);
      if( wndGrid.SelectionGetForCell( nColNo, nRowNo ) )
            return COLORREF( -1L );
LONG nCurSel = GetCurSel();
      if( nCurSel >= 0 )
      {
            clrText = GetItemTextColor( nCurSel );
            if( clrText != COLORREF( -1L ) ) 
                  return clrText;
      }
      return COLORREF( -1L );
}

The button control without handler attached on the dialog is not the source of the problem. You can even not click it and just press TAB key to switch focus from grid window to other dialog control. As you can see in the method’s source code above, if the combo box grid cell is selected, then the default text color is used. This is true independently from the focused state of the grid window. We think the colored text will work like you need if you replace the following lines in the method above:

 if( wndGrid.SelectionGetForCell( nColNo, nRowNo ) )
            return COLORREF( -1L );

With the following:

 if(         nColType == 0
            &&    nRowType == 0
            &&    ( dwHelperPaintFlags & __EGCPF_FOCUSED_CONTROL ) != 0 
            &&    wndGrid.SelectionGetForCellPainting( nColNo, nRowNo )
            )
            return COLORREF( -1L );

We need your help in reproducing this issue. Could you please modify the following simple test project in such a way that we have grid cells like you have in your real project and provide us with exact description of what we should click, press, move, drag and do to see the problem?

http://www.prof-uis.com/download/forums/TestHoveredButtonsForRon.zip

http://www.prof-uis.com/prof-uis/tech-support/support-forum/tab-control-gui-design-problems-61583.aspx#@lt;/p>

The main problem with drawing/not-drawing lines in the grid control depending on the type of its parent control is the following: it’s hardly possible to implement this for all the possible types of parent controls and for all the implementations of these controls in all the provided by Prof-UIS paint managers. It’s possible to find a really working and simple solution in scope of your project. For instance, you can leave some free space around the grid control.

Here is a picture to explain the problem.

http://www.prof-uis.com/prof-uis/tech-support/support-forum/cexttabpagecontainerwnd-mouse-click-events-61796.aspx#@lt;/p>

Thanks.

We coded the following test/sample project for you:

http://www.prof-uis.com/download/forums/TestContextMenuInTabPageContainerTabItemsForRon.zip

This the simple dialog based project with the tab page container control created inside the main dialog window. It demonstrates how to handle right mouse clicks on the tab items of the tab control inside tab page container window. These right clicks can be optionally handled in the tab page container class, in the main dialog class (used as parent window of the tab page container window) or even in both classes including up and down left mouse button events. You can simply display context menu instead of message box displayed in our test project. The ::GetCursorPos() Win32 API should be used for retrieving mouse cursor position which is needed in parameters of the CExtPopupMenuWnd::TrackPopupMenu() method.

This the simple dialog based project with the tab page container control created inside the main dialog window. It demonstrates how to handle right mouse clicks on the tab items of the tab control inside tab page container window. These right clicks can be optionally handled in the tab page container class, in the main dialog class (used as parent window of the tab page container window) or even in both classes including up and down left mouse button events. You can simply display context menu instead of message box displayed in our test project. The ::GetCursorPos() Win32 API should be used for retrieving mouse cursor position which is needed in parameters of the CExtPopupMenuWnd::TrackPopupMenu() method.

http://www.prof-uis.com/prof-uis/tech-support/support-forum/grid-question-61823.aspx#@lt;/p>

Here is a small test project which demonstrates the grid cell buttons like you need:

http://www.prof-uis.com/download/forums/TestHoveredButtonsForRon.zip

I started to get crashes when the bars states were loading from the registry. I traced the problem back to the function CExtControlBar::InternalFriendlyFrameWnd::SetOuterDockState and found out that for some reason there were 20 (!) bars with the ID AFX_IDW_DOCKBAR_FLOAT saved, and when they are loaded, in the last pass I got a crash in the highlighted line::

    for( i = 0; i < state.m_arrBarInfo.GetSize(); i++ )
    {
        CControlBarInfo * pInfo = (CControlBarInfo *)
            state.m_arrBarInfo[i];
        TRACE("\n%d]pInfo: %d ptr: %X hwnd: %X",i,pInfo->m_nBarID, pInfo->m_pBar, pInfo->m_pBar->GetSafeHwnd());
        ASSERT( pInfo != NULL );
        if( pInfo->m_pBar == NULL )
            continue;
        if(        (! pInfo->m_pBar->IsKindOf(RUNTIME_CLASS(CExtControlBar)) ) <= THIS CRASHED
            ||    ( ((CExtControlBar*)pInfo->m_pBar)->IsFixedMode() )
            ||    ( ((CExtControlBar*)pInfo->m_pBar)->IsFixedDockStyle() )
            )
        {
...

What I did, was to remove this piece of code from the function:

        if( pInfo->m_bFloating )
        {
            // need to create floating frame to match
            CMiniDockFrameWnd * pDockFrame =
                CreateFloatingFrame(
                    pInfo->m_bHorz ?
                        CBRS_ALIGN_TOP : CBRS_ALIGN_LEFT
                    );
            ASSERT( pDockFrame != NULL) ;
            CRect rcWnd( pInfo->m_pointPos, CSize(10, 10) );
            pDockFrame->CalcWindowRect( &rcWnd );
            pDockFrame->SetWindowPos(
                NULL,
                rcWnd.left, rcWnd.top, 0, 0,
                SWP_NOSIZE|SWP_NOZORDER|SWP_NOACTIVATE
                );
            CDockBar * pDockBar = (CDockBar *)
                pDockFrame->GetDlgItem( AFX_IDW_DOCKBAR_FLOAT );
            ASSERT( pDockBar != NULL );
            ASSERT_KINDOF( CDockBar, pDockBar );
            pInfo->m_pBar = pDockBar;
//             if( pInfo->m_bVisible )
//                 _mapCFV.SetAt( pDockFrame, 0 );
        } // if( pInfo->m_bFloating )
        else // regular dock bar or toolbar
...

Without this code, there are no crashes, and it seems that all the menus and bars are loaded properly.

1. Can you please explain what this piece of code is for?

2. Is it reasonable that I will have 20 bars with the same ID AFX_IDW_DOCKBAR_FLOAT?

3. What does it crash when this happen?

Thanks,

Ron.

 

 

 

When you see a floating toolbar on the desktop, you really see three windows:

1) Floating mini frame window. This is the CMiniDockFrameWnd window in MFC. This is the CExtMiniDockFrameWnd window in Prof-UIS.

2) There is only one child window inside floating mini frame window - the dock bar. This is the CDockBar window. It’s dialog control identifier is the This is the AFX_IDW_DOCKBAR_FLOAT
window value. The CDockBar class is derived from the CControlBar class. Nevertheless dock bars are inner components of both Prof-UIS and MFC, they are also control bars and both MFC and Prof-UIS save their states.

3) The child of dock bar is toolbar window which was switched into floating state.

This is the rule of both MFC and Prof-UIS: the parent window of re-dockable toolbar window is always dock bar window. There are four dock bars inside main frame window. They are created and docked near main frame’s sides. Their dialog control identifiers:
AFX_IDW_DOCKBAR_TOP, AFX_IDW_DOCKBAR_BOTTOM,
AFX_IDW_DOCKBAR_LEFT and
AFX_IDW_DOCKBAR_RIGHT. But all the dock bar windows in all the floating mini frames are having the AFX_IDW_DOCKBAR_FLOAT dialog control identifier. The dock bar windows are non-re-dockable control bars. The main frame’s dock bars are parent windows for control bars docked inside main frame window. The dock bar windows inside all the floating mini frame windows are parents for floating control bars. Both toolbars and dock bars are MFC control bars. Both MFC and Prof-UIS save state of all the control bars including dock bars. All the control bars must have unique dialog control identifiers. But AFX_IDW_DOCKBAR_FLOAT is the exception in both MFC and Prof-UIS. There is another similar exception in Prof-UIS
only: dynamic row/column like containers and tab containers for resizable control bars in Prof-UIS are also resizable control bars and they also have non-unique dialog control identifiers. But resizable control bars in Prof-UIS have their own state serialization and layouting/drag-n-dropping algorithms not based on MFC source code.

The assertion/crash described in your message can occur if you have created some toolbar or resizable control bar using the AFX_IDW_DOCKBAR_FLOAT dialog control identifier. This is not acceptable. Please check dialog control identifiers of all your control bars first of all. They should be unique. You will never have problems with them if their dialog control identifiers will be less than 29000.

This is from MSND:

_APS_NEXT_COMMAND_VALUE is the next symbol value that will be used for a command identification. The valid range for command symbol values is 0x8000 to 0xDFFF.

From here:

http://msdn.microsoft.com/en-us/library/6t3612sk(VS.71).aspx#@lt;/p>

MFC defines a set of its identifiers closer to 65535. Visual Studio resource editors can also generate identifiers close to 65535 but most of generated values start from 1 and growing. That is why we have used a range of identifiers 29000-32000 in Prof-UIS resources. The generated by Visual Studio identifiers should not intersect with Prof-UIS identifiers and it’s hardly possible because all the customer projects we ever saw has less than 10000 private identifiers. So, if your identifiers are less than 29000, then everything will be OK and they will not intersect with Prof-UIS nor with MFC.

But Microsoft defines command values to start after 0x8000 , please look into TN20 : http://msdn.microsoft.com/en-us/library/t2zechd4(VS.71).aspx#@lt;/p>

Which means that all the commands should start after 32,768

So, mayeb what you mean is that if my commands are after 32,768 that it should be fine...?

We are using a range lesser than 29000 in Prof-UIS based projects. If you use a range greater than 32000 like Microsoft advices, everything will be OK as well.

One thing that we do not understand:

You say that the dialog control identifiers should be less than 29000. However, this ID is the command ID that used in the menus to show/hide this dialog control bar.

As far as we know, commands IDs should be in the range of more then 32768. How can these two mechanisms will work? looks like there is a conflict here.

Please advise.

Dear Support,

We continued to investigate the code, and I don’t have any control bars using these numbers, and still I get crashes in this piece of code.

It looks like the pInfo->m_pBar is invalid - the CControlBar’s hWnd is 0xfeeefeee - which means it was deleted at one point.

How can this be possible?

We are now posponing a product release because of this bug, please try and give us some support on this ASAP.

Thanks,

Ron.

We suspect the problem is really caused by creating new/removing old control bars due to development process. Although Prof-UIS should not crash when loading states of not-existing control bars, we would like to ask you to remove the control bar state of your application from the system registry and try to run it several times. It would be interesting to know whether the assertions/crashes still occur?

OK - I will try this approach - but I think that Prof-UIS should be more forgiving, and not crash the application if a control-bar is not found. Please try and make it fail-safe.

Thanks,

Ron.

Another question - why do you create CMiniDockFrameWnd and not CExtMiniDockFrameWnd? This is from the same piece of code I commented off:

        if( pInfo->m_bFloating )
        {
            // need to create floating frame to match
            CMiniDockFrameWnd * pDockFrame =
                CreateFloatingFrame(
                    pInfo->m_bHorz ?
                        CBRS_ALIGN_TOP : CBRS_ALIGN_LEFT
                    );
            ASSERT( pDockFrame != NULL) ;
...

The CExtMiniDockFrameWnd class is derived from the CMiniDockFrameWnd class. The CFrameWnd::CreateFloatingFrame() method uses the CRuntimeClass* m_pFloatingFrameClass; property of the CFrameWnd () class for instantiating the CMiniDockFrameWnd object. Prof-UIS replaces this run-time information object with reference to the run-time class of the CExtMiniDockFrameWnd class (inside invocation of the CExtControlBar::FrameEnableDocking() static method). As a result, all the instances of floating mini frame windows are the CExtMiniDockFrameWnd windows. Besides, the CExtMiniDockFrameWnd class type is very required by all the Prof-UIS control bars. The CExtMiniDockFrameWnd windows have skinned caption and borders. So, if you see skinned floating mini frame windows, then they are instances of the CExtMiniDockFrameWnd class.

Hello.

http://www.prof-uis.com/prof-uis/tech-support/support-forum/cextribbon-bug-61809.aspx

Hello.

I want to display a menu in such a form.

Image 1:

Image2:

Is it difficult?

 

Yes. You should define a custom layout rule array for each button node in a ribbon group. All buttons should have only one item in the rule array which defines some visual informativenss of the button at the maximum effective informativeness level. As a result, the group of buttons will have a constant width because all the buttons in it does not change their visual look.

The most appropriate control is a palette menu. You can see this menu displayed from a toolbar chevron button. You can see a palette menu in the context menu displayed over the popup menu related dialog page in the ProfUIS_Controls sample application.

Hello.

I want to build such a ribbon menu.

Will it be impossible?

<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="Word.Document" name="ProgId" />
<meta content="Microsoft Word 12" name="Generator" />
<meta content="Microsoft Word 12" name="Originator" />
<link href="file:///C:\Users\ALEXBO~1.DOM\AppData\Local\Temp\msohtmlclip1\01\clip_filelist.xml" rel="File-List" />
<link href="file:///C:\Users\ALEXBO~1.DOM\AppData\Local\Temp\msohtmlclip1\01\clip_themedata.thmx" rel="themeData" />
<link href="file:///C:\Users\ALEXBO~1.DOM\AppData\Local\Temp\msohtmlclip1\01\clip_colorschememapping.xml" rel="colorSchemeMapping" />

<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves />
<w:TrackFormatting />
<w:PunctuationKerning />
<w:ValidateAgainstSchemas />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF />
<w:LidThemeOther>RU</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables />
<w:SnapToGridInCell />
<w:WrapTextWithPunct />
<w:UseAsianBreakRules />
<w:DontGrowAutofit />
<w:SplitPgBreakAndParaMark />
<w:DontVertAlignCellWithSp />
<w:DontBreakConstrainedForcedTables />
<w:DontVertAlignInTxbx />
<w:Word11KerningPairs />
<w:CachedColBalance />
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val="Cambria Math" />
<m:brkBin m:val="before" />
<m:brkBinSub m:val="--" />
<m:smallFrac m:val="off" />
<m:dispDef />
<m:lMargin m:val="0" />
<m:rMargin m:val="0" />
<m:defJc m:val="centerGroup" />
<m:wrapIndent m:val="1440" />
<m:intLim m:val="subSup" />
<m:naryLim m:val="undOvr" />
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" />
<w:LsdException Locked="false" Priority="39" Name="toc 1" />
<w:LsdException Locked="false" Priority="39" Name="toc 2" />
<w:LsdException Locked="false" Priority="39" Name="toc 3" />
<w:LsdException Locked="false" Priority="39" Name="toc 4" />
<w:LsdException Locked="false" Priority="39" Name="toc 5" />
<w:LsdException Locked="false" Priority="39" Name="toc 6" />
<w:LsdException Locked="false" Priority="39" Name="toc 7" />
<w:LsdException Locked="false" Priority="39" Name="toc 8" />
<w:LsdException Locked="false" Priority="39" Name="toc 9" />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" />
<w:LsdException Locked="false" Priority="37" Name="Bibliography" />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" />
</w:LatentStyles>
</xml><![endif]-->

<style type="text/css">
<!--
/* Font Definitions */
@font-face
    {font-family:"Cambria Math";
    panose-1:2 4 5 3 5 4 6 3 2 4;
    mso-font-charset:1;
    mso-generic-font-family:roman;
    mso-font-format:other;
    mso-font-pitch:variable;
    mso-font-signature:0 0 0 0 0 0;}
@font-face
    {font-family:Calibri;
    panose-1:2 15 5 2 2 2 4 3 2 4;
    mso-font-charset:204;
    mso-generic-font-family:swiss;
    mso-font-pitch:variable;
    mso-font-signature:-1610611985 1073750139 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
    {mso-style-unhide:no;
    mso-style-qformat:yes;
    mso-style-parent:"";
    margin:0in;
    margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:12.0pt;
    font-family:"Times New Roman","serif";
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;}
.MsoChpDefault
    {mso-style-type:export-only;
    mso-default-props:yes;
    font-size:10.0pt;
    mso-ansi-font-size:10.0pt;
    mso-bidi-font-size:10.0pt;}
@page Section1
    {size:8.5in 11.0in;
    margin:56.7pt 42.5pt 56.7pt 85.05pt;
    mso-header-margin:.5in;
    mso-footer-margin:.5in;
    mso-paper-source:0;}
div.Section1
    {page:Section1;}
-->
</style>

<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
</style>
<![endif]-->

It is a palette menu, which is fully supported in Prof-UIS. You can find an example of it in in the <i>Popup Menu</i> of the <span class="newgreen">ProfUIS_Controls</span> sample. The context menu displayed over this dialog page contains a popup sub menu with a palette layout.<o:p></o:p>

<o:p> </o:p>

Hello.

About the matter mentioned above.

The problem was settled.

Thanks,

 

By the way,

When the node inside is displayed,

I want to immobilize the width of the ribbon group

Please explain more about what’s wrong with the width of the ribbon group with buttons displayed on the screenshot? This width is computed by the ribbon bar automatically. It’s the minimal possible width which should allow to display all the buttons inside the group.

Hello.

I made a variable menu and a fixed menu in a ribbon bar.

A position of the display of the fixed menu is changed by a variable menu.

I think that a user is hard to treat it.

Therefore, I want to immobilize the width of the variable menu.

The above is a reason.

Is there an opinion?

 

The width of a ribbon group is computed using the width of its inner ribbon buttons. That is what we see in both your screen shots and everything is correct in both cases.

In my application, users occasionally need to enter characters that are not on a standard keyboard.  For instance if they wish to enter the Yen symbol, they hold down Alt and type 157 on the number keypad (not the top row of keys) and release alt.  This will produce the Yen sign ¥ (I just used that technique here to generate a Yen symbol).

This works in any Windows app, except Prof-UIS based ones.  When I recently added Prof-UIS support to my application, users are no longer able to generate special symbols using Alt+Keypad anymore.  To make sure that this wasn’t just something I am doing wrong, I downloaded 2.83 and built Prof-Studio using Visual Studio 2008.  Sure enough, in any of the edit windows in the Prof-Studio sample, I cannot enter special symbols via Alt+keypad.  Instead most special symbols generate question marks (?) instead in an ANSI build.  In a Unicode build, most generate an unprintable character.

By contrast, if I open Notepad, or simply create a basic MFC dialog app (no Prof-UIS support) with an edit box, Alt+keypad entry works.

We are looking to ship soon and could really use a comment on this.  I posted this problem a couple of months ago, but never received a reply.  It would really be appreciated if you could offer some sort of comment on this issue.  Please feel free to ask questions if anything is unclear.

I have a floating bar. Inside the bar I have CExtTreeGridWnd with two columns. The columns width are set with ExtentPercentSet.

In some place in the flow I need to resize the bar. I do it using a call to SetInitDesiredSizeFloating. The problem is that the grid does not get the call, and the columns percent is not updated until I resize the bar with the mouse.

Is there a better way to progrematicaly resize an existing bar?

Is there a way to force the grid to update the columns sizes?

Are you using the following code at the end of tree grid initialization?

    wndTreeGrid.OnSwUpdateScrollBars();
    wndTreeGrid.OnSwRecalcLayout( true );

Are you using the CExtControlBar class "as is" or you have derived your own control bar class which may eat size changing notifications somehow? If would be also very interesting to take a look at the complete tree grid initialization code.

I use a derived class, but it does not eat events at all. it doesn’t even have any message map macros.

I have these two lines, but still, the grid does not adjust the columns unless I manualy resize the bar.

This is what I do when I need to show the bar:

        POINT pt;
        GetCursorPos(&pt);
        SetInitDesiredSizeFloating(CSize(200, 300));
        SetInitDesiredPosFloating(pt);
        FloatControlBar(pt);
        CFrameWnd* pFrame = GetParentFrame();
        pFrame->RecalcLayout();
        pFrame->SendMessage(WM_NCPAINT); 
        ((CFrameWnd*)AfxGetMainWnd())->ShowControlBar(this, TRUE, FALSE);
        m_pPropTree->OnSwUpdateScrollBars();
        m_pPropTree->OnSwDoRedraw();
        m_pPropTree->OnSwRecalcLayout( true );

And still, it does not resize/update the columns widths in the tree grid.

This source code is absolutely OK. It would be much more interesting to take a look at the tree grid’s initialization source code where all the styles are applied and columns inserted.

Called at initialization time:

bool CMyTreeGrid::Init()
{
    SiwModifyStyle(
        (__ESIS_STH_NONE|__ESIS_STV_ITEM)        // Item scroll window styles
        | __EGBS_SFB_FULL_ROWS                    // Selection/focus type - full rows
        | __EGBS_DYNAMIC_RESIZING                // Resize rows/columns on-the-fly
        | __EGBS_RESIZING_CELLS_OUTER            // enable row/column resizing
        ,0, false);

    SiwModifyStyleEx(
        __EGBS_EX_CELL_TOOLTIPS_INNER
        | __EGBS_EX_CELL_EXPANDING_INNER
        | __EGWS_EX_PM_COLORS
        | __EGBS_EX_CORNER_AREAS_3D
        | __EGBS_EX_CORNER_AREAS_CURVE
        | __EGBS_EX_HVI_EVENT_CELLS
        ,0, false);

    BseModifyStyleEx(__EGBS_BSE_EX_PROPORTIONAL_COLUMN_WIDTHS);

    OuterRowCountTopSet(1, false);
    OuterRowHeightSet(true, 0, 0);
    ColumnAdd(2, false);
 
    CExtGridCellHeader* pCellHdr = (CExtGridCellHeader*)GridCellGetOuterAtTop(0, 0, RUNTIME_CLASS(CExtGridCellHeader));
    pCellHdr->ExtentPercentSet(0.4);

    pCellHdr = (CExtGridCellHeader*)GridCellGetOuterAtTop(1, 0, RUNTIME_CLASS(CExtGridCellHeader));
    pCellHdr->ExtentPercentSet(0.6);

    g_PaintManager->LoadWinXpTreeBox(m_iconTreeBoxExpanded, true);
    g_PaintManager->LoadWinXpTreeBox(m_iconTreeBoxCollapsed, false);

    return true;
}

The three grid initialization code is absolutely OK. We created a small test project with a tree grid inside a control bar and your tree grid initialization code "as is". We failed to reproduce the problem with it.

TestTreeGridInFloatingBar.zip

Please help us to reproduce the problem.

Dear Support,

Thank you for the application - I was able to reproduce the bug easily with your application.

Add this command handler to the CMainFrm, and a matching command to the main frame menu:

void CMainFrame::OnCommandReopen()
{

    POINT pt;
    GetCursorPos(&pt);
    m_wndResizableBar.SetInitDesiredSizeFloating(CSize(200, 300));
    m_wndResizableBar.SetInitDesiredPosFloating(pt);
    m_wndResizableBar.FloatControlBar(pt);
    CFrameWnd* pFrame = m_wndResizableBar.GetParentFrame();
    pFrame->RecalcLayout();
    pFrame->SendMessage(WM_NCPAINT); 

    ShowControlBar(&m_wndResizableBar, TRUE, FALSE);

    m_wndTreeGrid.OnSwDoRedraw();
    m_wndTreeGrid.OnSwRecalcLayout( true );
}

Now, run the application, close the bar, and press the command - the bar will re-appear.

You will see that when the bar re-appear the columns of the tree in it are not divided 40-60 until you resize the bar - that’s the bug.

Thanks,

Ron.

 

We have done just as you explained. But everything seems OK. Here is the updated source code and compiled binaries:

http://www.prof-uis.com/download/forums/TestTreeGridInFloatingBar2.zip

Dear Support,

I just ran your executable and the bug is there...

To see it more clearly do this - before closing the bar make it very wide, so that when you re-open the column separator will not be shown at all, then resize the bar you’ll see the columns separator popping.

Ron.

 

Were you able to see the bug now?

The parent is CExtControlBar. I create the tree grid, and it’s parent is the CExtControlBar like this in a CExtControlBar derived class:

m_pPropTree = new CExtNSB<CMyTreeGrid>;
m_pPropTree->Create(this);

I resize the CExtControlBar using the methods mentioned above, which resizes the control bar,  and I guess does not call the child WM_SIZE.

It is not enough to invoke the CExtControlBar::SetInitDesiredSizeFloating() method. You should re-compute the layout of control bar’s parent frame window which is a floating mini frame window if the control bar is in the floating state. The CChangeFloatingSizeView::OnButtonFloat() method in the following test project does this:

http://www.prof-uis.com/download/forums/ChangeFloatingSize2.zip

Here is the method’s source code:

void CChangeFloatingSizeView::OnButtonFloat() 
{
      UpdateData( TRUE );
CExtControlBar & bar = ( STATIC_DOWNCAST( CMainFrame, GetParentFrame() ) ) -> m_wndResizableBar;
CPoint pt( m_nEditLeft, m_nEditTop );
CSize sz( m_nEditWidth, m_nEditHeight );
      bar.SetInitDesiredPosFloating( pt );
      bar.SetInitDesiredSizeFloating( sz );
      bar.FloatControlBar( pt );
CFrameWnd * pFrame = bar.GetParentFrame();
      ASSERT_VALID( pFrame );
      if( pFrame->IsKindOf( RUNTIME_CLASS( CMiniDockFrameWnd ) ) )
      {
            pFrame->RecalcLayout();
            pFrame->SendMessage( WM_NCPAINT ); 
      }
}

This is exactly what I’m doing already. It does not work.

The grid control inside the bar does not get resized when this code is reached. Maybe there is a bug in eth bars?

What is the parent window of your grid window? Is it a control bar or if there is some window between the grid and the control bar? We know that the grid window re-computes the layout of its parts correctly when it receives a WM_SIZE message. If the layout is not updated then the grid window was not resized or it didn’t receive the WM_SIZE message due to any reason like the parent class method was not envoked etc.