Forum

Hello.

I want to change English message for a Japanese message.

Please teach a good method.

There is one problem with translating these color names into Japanese: The CExtGridCellColor::GetColorName() method is virtual in v.2.83, but not virtual in 2.82. You should mark it as virtual if you are using 2.82 or earlier, create your own CExtGridCellColor-derived class and implement this virtual method.

Hello.

May I use __EGCS_EX_USER_STYLE_00 ?

Dear Sir,

How to Place the Company Logo on the Top DockBar of the SDI Frame Window?

Best Regards,

Hello,

I have an edit box that is numbers only and when the user enters something like a letter. It shows the stadard message unacceptable character. The problem is when it shows the box even though its not over the CExtGroupBox  that surrounds the edit control, it messes up the painting of the label on the group box. Have you guys seen this or know how to fix it?

Thanks,

CJ

Is the fix to the CExtGridBaseWnd::OnLButtonUp method going to be in the next release of the Prof-UIS?

Yes.

Does it work on columns header as well?

Hello,

I reported several problems in version 2.83 - were you able to reproduce them? Are you going ot fix them for the coming release? When is the release due?

Thanks - Ron.

Well, I hope they are working very hard on fixing the bugs that they don’t have time to answer...

I sent you a while ago a clip of a flicker problem when resizing a two columns tree grid when the grid was not in focus before the beginning of the column drag.

I see that this bug still persist in 2.83

Any pointers for using auto menu in an mdi frame instead of an sdi frame? It doesn’t seem to want to display the doc related menu after running the example VBS.

MenuInfoAdd, it’s a good thing.

Yes, you are right. But some people would prefer to see one universal menu in MDI interface.

Even though we are using your fabu toolkit, our app is still a bit in the dark ages as far as menu processing goes...

Would you tell us what areas remain dark so that we can help you?

I have no idea what is causing this, and I cannot reproduce it in your sample application.

Our main frame has been updated to use Prof-UIS, even though the frame class itself is from another library.  This class ultimately is derived from CMDIFrameWnd.  That said, I have implemented the following:

 class CMyFrame : public CExtNCW< SECWorkbook>,

public CExtDynamicBarSite,

public CExtCustomizeSite

and in the OnCreate of the frame:

CExtControlBar::FrameEnableDocking( this );

CExtControlBar::FrameInjectAutoHideAreas( this );

CExtDynamicBarSite::Install( this );

I create my CExtDynamicControlBar s on the fly utilizing CExtDynamicBarSite::BarAlloc.  The dynamic control bars show up just fine.  I can dock them, float them, MDI them.  But if I unpin them, they go into the auto hide mode, I see the tab button.  I click on something else, the bar hides.  I mouse over to the tab button, the button disappears and the hidden bar, of course, never reshows itself.  It is possible that if I dock another window to the same edge the tab might come back, but it almost certainly will disappear yet again as soon as I do the aforementioned steps. 

I’ve been trying to figure out what might possibly be causing this behavior to no avail.  Using a message spy program on both your sample and my application shows that in my application the CExtTabWnd is not getting any timer messages or paint messages, though it continues to receive mouse messages.  If I debug into the mouse handler of CExtTabWnd, it says although there are apaprently visible buttons, the mouse isn’t over them.

Any suggestions would be greatly appreciated...

Kevin Murray

Well, you are correct that WM_SIZEPARENT is not getting through.  I don’t know where it’s going, but it isn’t getting through.  Whenever I dock another window to the same side as the missing tab(s), they come back, but again, as soon as they are used they go away.  I’ll do some investigating and try to determine why the message dies...

Kevin Murray

Your investigation needs the presence of all the UI related source code. Otherwise you can only exclude the usage of components available as binaries only to come to conclusion about who eats messages and modifies the default behavior of the frame window. Some additional information. When the frame window’s size becomes changed, it invokes the CFrameWnd::RecalcLayout() virtual method which simply invokes the CWnd::RepositionBars() method. Dialog based sample applications in Prof-UIS with control bar windows invoke the CWnd::RepositionBars() method from the dialog’s OnSize() handler method. The CWnd::RepositionBars() method sends a WM_SIZEPARENT message to all the child windows and allows them to take up the required space near window borders. But the CWnd::RepositionBars() method and WM_SIZEPARENT message can also be used for calculating the rest free space which is free of any bars in the center of the window and this center space is used for a view window in SDI applications and for an MDI client area window in MDI applications. So, the CWnd::RepositionBars() API and WM_SIZEPARENT message represent an important and very frequently used feature of MFC rather than of Win32 API (though the WM_SIZEPARENT preprocessor symbol starts from WM).

Well, now I’m to the point where the tabs don’t repaint themselves.  You can mouse over the tab, the window shows itself.  Move away, it hides.  Move to another tab, the tabs disappear and no windows show themselves.  It will stay this way till I can force a repaint, say by switching to another application then switching back.  Any ideas on this one?  I hope it is a simple repaint issue, and not that the tab windows think they don’t have any tabs any more.  But if I debug, as soon as I switch into the debugger, it says all is good and the tabs will redraw.  I’ve tried forcing a RedrawWindow() for the auto-hide areas on WM_NCACTIVATE, but that isnt’ working.  Tried Invalidate() as well; tried them both together. 

Kevin Murray

Please check the following:

1) Your main frame should have the WS_CLIPSIBLINGS|WS_CLIPCHILDREN styles set on (use the SPY++ utility for that). Although Prof-UIS tries to forcibly set these styles to the main frame window, please check whether they are really added.

2) Do you have some painting code based on CDC::GetDC() API or ::GetDC() API invoked for the main frame window with flags for retrieving the entire window/client DC without any clipping?

Such fantastic problems require similar fantastic approaches for resolving them: in the hardest case you will need to comment out some parts of your project one by one until the problem is gone and then try to understand what causes the problem.

Once again, you guys prove you know your stuff. :)

Turns out, after heavy debugging, the base class we are using has a member they call m_pMDIClientArea, which overrides OnPaint.  So as long as I override OnPaint, let the base class do its thing, then do the repaint of the control bars, all is well.

My question to you now is this:

void CMyFrame::OnPaint()

That’s what I have.  The hide animation, though, is now terribly slow.  The CExtDynAutoHideArea’s do not seem to respond to a RedrawWindow() request.  Is there a more effecient way to repaint these in the OnPaint handler so the animation is smoother?

K.

The WM_PAINT, WM_ERASEBKGND and WM_NCPAINT message handlers should draw something into the device context and should not do anything with windows including their states, positions and visibility. Otherwise, these message handlers will cause further sending of these messages to the same and/or other windows. Although what was just said above is true, preventing the window procedure of the MDI client area window from receiving the WM_ERASEBKGND message can cause the MDI interface to work incorrectly.

Could you send us source code of your improved frames and source code of class which subclasses the MDI client area window (type of m_pMDIClientArea) ?

Unfortunately I cannot send you the source code as it is a purchased product, much like your library. 

I can tell you they call RepositionBars(...reposQuery) to adjust the client rectangle before they do their drawing.  However, they end with the following:

RedrawWindow(NULL, NULL, RDW_INVALIDATE|RDW_ERASE|RDW_ALLCHILDREN);  

It would be extremely interesting to know what the non-Prof-UIS UI classes really do in your project? We have a lot of test applications which modify different behaviors of MDI, SDI and dialog based applications. These test applications have been collected as replies and suggestions to Prof-UIS users during more than five years. It’s possible we can provide you with a ready-to-use solution which allows you to remove the code conflicting with Prof-UIS.

Concerning my request about the PageContainer. Please have a look at the PageContainer example especially at the “Custom-drawn page container” which is the free floating window within this demo. Focus on the first part called Dialog including the Label, Check1, Check2 and Check3 items. If you stretch the window horizontally these items are stretched accordingly. If you stretch the window vertically the items are not stretched at all. Imagine instead of the Label, Check1, Check2 and Check3 items you have a picture in the Dialog item. If you stretch the window horizontally the picture could always have the same width as the window.

That is where my problem starts to arise. If the picture gets stretched in width it should also be stretched in height. Since the height of the dialog keeps the initial height the picture has no room to gain in height. As I stretch the window horizontally I would need the Dialog item to be stretched in height as well as in width. Therefore the other items such as “Custom-drawn Shortcut List Window”, “Listview Control” and “Web Browser Control” should dynamically move up or down, depending on the space I need for my Dialog item.

Please let me know if there is a way to solve my picture issue.

Best regards

The CExtPageContainerWnd class supports two types of the layout behavior:

1) Like in Outlook 98/2000/XP. Only one page is expanded and it’s stretched to the entire available height. Other pages are collapsed. The scrollbar like area is never used.

2) Like in 3D Studio MAX. Many pages can be expanded and/or collapsed at the same time. Scrollbar like area is available.

The PageContainer sample provides both options (available from the menu). Please let us know whether you need the Outlook mode or you are looking for some other layout which has not been implemented yet?

Concerning my request about the PageContainer. Please have a look at the PageContainer example especially at the “Custom-drawn page container” which is the free floating window within this demo. Focus on the first part called Dialog including the Label, Check1, Check2 and Check3 items. If you stretch the window horizontally these items are stretched accordingly. If you stretch the window vertically the items are not stretched at all. Imagine instead of the Label, Check1, Check2 and Check3 items you have a picture in the Dialog item. If you stretch the window horizontally the picture could always have the same width as the window.



That is where my problem starts to arise. If the picture gets stretched in width it should also be stretched in height. Since the height of the dialog keeps the initial height the picture has no room to gain in height. As I stretch the window horizontally I would need the Dialog item to be stretched in height as well as in width. Therefore the other items such as “Custom-drawn Shortcut List Window”, “Listview Control” and “Web Browser Control” should dynamically move up or down, depending on the space I need for my Dialog item.

Please let me know if there is a way to solve my picture issue.



Best regards

The custom drawn page container uses a 3D Studio Max layout and behavior. The mutual layout of page windows is computed according to the real height of each window. The page container control can change the width of all pages but can never change their height. So, if you need some page window with an automatically adjustable height, you should handle the WM_SIZE message in this page window, compute the required height according to the changed width and let the window resize itself vertically using the SetWindowPos() or MoveWindow() APIs if needed. If the page window resizes itself vertically and its window has the WS_VISIBLE style (i.e. the page is not contracted), the page container’s CExtPageContainerWnd::UpdatePageContainerWnd() method should be invoked to re-compute the mutual layout of all page windows. You can simply invoke

( STATIC_DOWNCAST( CExtPageContainerWnd, GetParent() ) ) -> UpdatePageContainerWnd();

I‘ve been trying to use your latest suggestions, but I was not successful. Should I call UpdatePageContainerWnd with false or true? If I call the SetWindowPos within WM_SIZE of the panel it triggers a new WM_SIZE.

In order to save time, I would like to ask you, if you could extend the PageContainer example program with the behavior I am looking for. In my case the height of the panel under Dialog with the Label, Check1, Check2 and Check3 should always have the same length as the width (width == height). As you drag the “Custom-draw page container” the Dialog panel should grow or shrink in height accordingly.

I have a CExtTreeGridWnd object functioning fine except the scrolling feature. The scrollbars function fine except when I select a cell that is horizontally scrolled onto the screen. In this case, the scrollbars automatically reset such that the first column is displayed. For example, there are 20 columns in the grid. When viewing (done by scrolling) the 20th column, the 1st column is no longer visible. If I click on a cell in column 20, the H-scrollbar is set to the far left so that the 1st column is visible (and the 20th column is not visible.) I would like to prevent this auto-scrolling. I am using the __EGBS_SFB_FULL_ROWS feature. See grid styles below.

On a different note, I would like to fix the first three columns in grid. That is, when scrolling horizontally, only the last 17 columns scroll. Is this possible?

Thanks,

Gil

//Enable

SiwModifyStyle( __ESIS_STH_PIXEL

After further testing, I found that overriding  the OnGbwDataDndIsAllowed method and returning a value of true causes the scrolling problem described in the initial email.  If I comment out this function, clicking on a cell in the far right column does not auto-scroll to the 1st column of the grid. Any thoughts?

As well, my tree grid has two layers of nodes. As it is now, when I double-click anywhere on the row of the top node, the node is collapsed or expanded. It there any way to limit the collapse/expand functionallity to the plus/minus button?

Gil

Hi.

I want assign icons with all my items in tree. So... I try use simple code:

parent = m_tree->ItemInsert( NULL );

m_tree->ItemExpand( parent );

CExtGridCell * cell = m_tree->ItemGetCell( parent, 0, 0, RUNTIME_CLASS( CExtGridCellStringDM) );

cell->DataProviderGet()->IconInsert(&m_DeviceIcon,1);

cell->IconIndexSet(1);

cell -> TextSet(L"Simple text");

But in this case I see icons and don`t see text. Where I make mistake?

If I insert icon with greater height as text-height then GridCellRectsGet() will use height (of icon) for computing height of cell?

In a grid cell, any icon is used without resizing and any other adjustments. You may need to increase the row height and/or column width for the grid cell with a large icon. The best way is to initialize all grid cells in some row/column and then invoke the CExtGridWnd::BestFitColumn() and/or CExtGridWnd::BestFitRow() methods.

Is there any way to disable theming in prof-uis app?

I looked at the FormEditor sample ( Prof-UIS v283 + VS2005 ), the project file already include additional manifest file , manifest_x86.xml, and it’s already calling InitCommonControls() function inside CFormEditorApp::InitInstance() function, but it’s still loading native XP theme. I also try calling CExtUxTheme::EnableTheming( FALSE), which didn’t make any differen If it’s ever possible to use XP visual style instead of themes ? If XP visual style is used,  I guess the menu is still based on menu bar, not win32 menu ? 

Thanks

Would you clarify your question? What do you mean by “disable theming”? What the effect you want to achieve? Would you send us some screenshots?

What we tried to do is : add an option to our app so it can either use the "themes" provided by prof-ui, or simply default to  MFC/Win32 which can be controlled by a manifest file ( i.e. with native MFC app,  you can enable Windows XP Visual Style or look and feel by adding a manifest file to the project, and calling InitCommonControls() during the start up )

You may ask why don’t we just use native XP theme provided by prof-uis, well, there is still difference between prof-ui native XP theme and native MFC app, I will create a screenshot shortly

So in a nutshell, the question is : after the integration of prof-uis, is it possible to go back to the old MFC app without rolling back the changes in the code ?

Thanks

You asked a short question in a nutshell but we have no short answer for it. If you integrate Prof-UIS grids into your project, you will have to recode parts of your project after rolling back to MFC only UI because grids are not present in MFC. But we do not think you have any reason to remove the Prof-UIS grids. If you use Prof-UIS toolbars and menus without advanced features like embedded popup list boxes, undo/redo/color/date-picker menus, then you can switch back to MFC easily. Besides there is no problem with common controls and dialogs if you are not using any Prof-UIS methods of these controls. You can roll back to MFC by changing only class names if you are using Prof-UIS classes which are mostly re-painted versions of other well known controls. But we think Prof-UIS provides much more than simple re-painting and you should decide whether to use or not to use it.

Typing second time after logging me out after posting first message :(((

Ok I’ve found 2 problems in tree grid. Here is VS2005 project with compiled demo exe: http://rrrado.szm.sk/grid_bug.rar

1. Print preview draws second line shifted to left ("98" should be under "313")

2. HoverInfoGet().m_dwAreaFlags sometimes does not work in CChildView::OnContextMenu. Sometimes it returns __EGBWA_NOWHERE althought mouse pointer is above valid cell. You can get it when you select some unselected cell/row with left mouse button and then try to invoke context menu using right mouse button. Maybe you’ll have to do this 10 times to get my error message.

Can you check it please? Thank you.

We would like to discuss a couple of issues:

1) The VK_LEFT and VK_RIGHT keys are processed by the CExtTreeGridWnd control (in the CExtTreeGridWnd::OnGbwAnalyzeCellKeyEvent() method). It is possible to change the behavior of these keys so that when pressed they collapse/expand rows only, scroll only, collapse/expande by default and scroll with some modifier key (VK_SHIFT or VK_CONTROL). We would like to know your point of view. We assume the current behavior provided by the CExtTreeGridWnd::OnGbwAnalyzeCellKeyEvent() virtual method is too simple and we can provide some new and customizable behavior instead.

2) We have re-tested the hit-testing results again and we never get nowhere code. May be we need to do some special sequence of steps to get it?

1)  it depends on tree size and structute. There is not a big usage difference in my tree so you could check standard windows tree behaviour for this

2) in my project resize 2nd column to prevent tooltip.

- Left click at "313" to select row, right click at 313

- Left click at "98" to select row, right click at 98

- back to beginning until "NOWHERE!" message box (there is random # of repetiotions needed - from 2 to 10)

Maybe you was trying it with another prof-uis version ? (You could try my exe with 2.82 debug dll)

The current version of CExtPPVW requires all the grid cells to have valid, non-NULL pointers. Although, any grid supports NULL pointers in any cell locations, typically the grid controls become completely initialized with grid cells. You initialize the tree grid using the following code at the end of the CChildView::PreSubclassWindow() method:

      CExtGridCellNumber *item;
      item = (CExtGridCellNumber *)ItemGetCell(it,0,0,RUNTIME_CLASS(CExtGridCellNumber));
      item->_VariantAssign(22);
      item = (CExtGridCellNumber *)ItemGetCell(it,1,0,RUNTIME_CLASS(CExtGridCellNumber));
      item->_VariantAssign(313);

      it = ItemInsert( NULL, ULONG(-1), 1 );
      item = (CExtGridCellNumber *)ItemGetCell(it,1,0,RUNTIME_CLASS(CExtGridCellNumber));
      item->_VariantAssign(98);

      item = (CExtGridCellNumber *)ItemGetCell(it,0,0,RUNTIME_CLASS(CExtGridCellNumber));

Hello.

I may have still inquired it.

Is not the setting of print pages possible?

Thanks,

Hello.

I can appoint print pages when I make it DoPrintDoc(true).

I want to use this function by all means. 

Will there be any problem?

void CExtPPVW_HostWnd::OnPreviewPrint()

{

 if( m_pPpvPrintable == NULL )

  return;

 GetParent()->ShowWindow( SW_HIDE ); // hide container window

HWND hWndOwn = GetSafeHwnd();

 ASSERT( hWndOwn != NULL );

 m_pPpvPrintable->DoPrintDoc( true );

The CExtPPVW template class is derived from the CExtPPVW_Printable helper class which has the following two bool properties: m_bUsePrintDialogFromOutside and m_bUsePrintDialogFromPreview. Both of these properties are set by default to false. The m_bUsePrintDialogFromPreview property defines whether the standard print dialog should be displayed when the Print button is clicked in the inner toolbar of the print preview window. The m_bUsePrintDialogFromOutside property defines whether the standard print dialog should be displayed when the ID_FILE_PRINT command is handled by the CExtPPVW-based class from outside the print preview UI. You can set them to true to see the dialog you need.

Hello.

I carry it out with a mode for mbs-Debug.

Assert appears.

m_bUsePrintDialogFromPreview = true

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

DLGPRNT.cpp

int CPrintDialog::DoModal()

{

 ASSERT_VALID(this);

 ASSERT(m_pd.Flags & PD_ENABLEPRINTHOOK);

 ASSERT(m_pd.Flags & PD_ENABLESETUPHOOK);

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

After I was troubled

I copied an ExtPrint.cpp source, and Assert did not appear.

The problem was settled. 

Hello.

When I am for release, non-display a theme bar

When I am for "Debug", I want to display a theme bar.

Is there the good method?

I think that I have part in this removal... I asked for this to be removed if the last column is to occupy the whole width of the grid.

You removed it altogether even if the last column does not reach the end of the grid, and then it looks a little weird...