Forum

Dear,

I’d like to put the AdoRecordView(CExtGridWnd) into CExtControlBar.

In my application that I want to make 5~6 dockable windows display the contents from MS SQL, respectively.

Please show me the simple example code.

How can I use png images instead of simple .bmp in my UI? First of all I interested in extended toolbar buttons.

Hello,

I’m using CExtGridWnd in my dialog.

I have to apply some logic after user has finished edit the cell.

Is there some way to get a notification message in my dialog box window procedure?

Or there is another way to handle this?

I’ll appreciate some example of sourcecode.

Thanks.

Hi,

Thanks for the prompt responce.

The first method works just fine for me.

Hi,

I’m using a CExtBarColorButton toobar button using the same code as in your StyleEditor sample app. I want to separate out the action performed when the users clicks the icon and when the click the drop down arrow. At present clicking on either one drops down the color pallete.

Instead what I want is when the user clicks on the icon I apply the current color and the color pallete window *does not* appear. If they click on the drop down arrow the color pallete window works as in the sample app. How can I do this?

Also is there a way to specify the colors used in the color pallete drop down window?

Thanks, Neville

Hi

If you try to remove all property stores from CExtPropertyGridComboBoxBar you get an assertin error. The problem,i think, is in CExtPropertyGridComboBoxBar::AssertValid() in

Hi,

How can I make a read-only column in the grid(CExtGridWnd)?

Thanks.

pCellVariant->ModifyStyle( __EGCS_READ_ONLY | __EGCS_NO_INPLACE_CONTROL);

Hi,

I’m using  a grid (CExtGridWnd), but the header cutting-off the bottom part of some letters from title.

How can I increase the height of the grid header?

Thanks.

Hi,

I am trying to get ctrl-c and ctrl-v working to allow me to cut and paste data between grid cells. The popup menu with the cut and paste options works correctly, however the shortcut keys (ctrl-c and ctrl-v) do not. They seem to work ok on the Prof-UIS PropertyGrid sample and I am not sure what I need to do my app to make them work.

I suspect that my main menu accelerators for ctrl-c and ctrl-v are interfering with the commands before the property grid gets a chance to get the messages. Ideally, what I would like would be for the copy and paste options on my main menu to be enabled/disabled depending on if the current cell data can be copied and/or pasted. Is this possible to do, maybe on an ON_UPDATE_COMMAND_UI message?

My property grid is located on a CExtCommandBar, which is attached to the CMainFrame. I have tried overriding the OnCmdMsg function in my command bar dialog to route the message ID_EDIT_COPY to the property grid but I just cannot get it to work correctly.

Any suggestions would be much appreciated!

Thanks

Hi,

I want to use the data grid(CExtGridWnd) in my dialog.

Could you please send me a simple project.

Some columns should be read only.

Cells new/changed values should be checked on the specified range.

Thanks.

HI,

The tooltip sample message was working fine. we would like to know whether is there a way to display the message on any window (CView or any other)?

email:sundar@cynaptix.com

regards

sundar

Hi,

I tried to display it on the View , when the View is maximised i am not able to see the tooltip message . I would like to see the tooltip message on the mouse pointer location. How to achieve this ?

regards

sundar

To help you, we coded a simple MDI application. The view window in the MDI child frame window draws a small red rectangle. You can see a balloon tip over it. Please download the sample project from here. The source code is very simple. We added the following members to the CTestView view class:

    CExtPopupMenuTipWnd m_wndCoolTip;
    CRect m_rcToolRect;

CTestView::CTestView()
    : m_rcToolRect( 50, 50, 100, 100 )
{
    // TODO: add construction code here
 
}

void CTestView::OnDraw(CDC* pDC)
{
    CTestDoc* pDoc = GetDocument();
    ASSERT_VALID(pDoc);
    // TODO: add draw code for native data here
 
    pDC->FillSolidRect( &m_rcToolRect, RGB(255,0,0) );
}

Finally, we have added the WM_MOUSEMOVE message handler to make cool tip window working:
 
void CTestView::OnMouseMove(UINT nFlags, CPoint point) 
{
    // TODO: Add your message handler code here and/or call default
 
    if( m_rcToolRect.PtInRect( point ) )
    {
        if(  m_wndCoolTip.GetSafeHwnd() == NULL
            || (m_wndCoolTip.GetStyle()&WS_VISIBLE) == 0
            )
        {
            CRect rcTrack = m_rcToolRect;
            ClientToScreen( &rcTrack );
            m_wndCoolTip.SetText( "cooltip" );
            m_wndCoolTip.Show( this, rcTrack );
        }
    }
    else
        m_wndCoolTip.Hide();
 
    CView::OnMouseMove(nFlags, point);
}

 I use v2.50.

  This code make assert error

 " m_pCombo->PropertyStoreRemove(-1); "

 I read T-S forum.

 and I found same case.
<TABLE style="BORDER-TOP: #aaaaaa 2px solid; BORDER-COLLAPSE: collapse" cellSpacing=0 cellPadding=6 width="100%" border=0>
<TBODY>
<TR>
<TD>

 Please solve this problem.

Please update the source code for the CExtPropertyGridComboBoxBar::PropertyStoreRemove() method in the ExtPropertyGridWnd.cpp file:

bool CExtPropertyGridComboBoxBar::PropertyStoreRemove(
    INT nPos // = -1 // if -1 - remove all
    )
{
    ASSERT_VALID( this );
    if( nPos < 0 )
    {
        m_arrPropertyStores.RemoveAll();
        if( GetSafeHwnd() != NULL )
            ResetContent();
        return true;
    }
    if( nPos >= PropertyStoreGetCount() )
    {
        ASSERT( FALSE );
        return false;
    }
    DeleteString( UINT(nPos) );
    m_arrPropertyStores.RemoveAt( nPos );
    return true;
}

  I edited that and recompiled lib & dll files.

  but same assert error come from.

If you have a page that contains something like this:

+----------------------------+
| Static Text                |
+----------------------------+
|                            |
|                            |
|                            |
|                            |
| CListBox                   |
|                            |
|                            |
|                            |
|                            |
+----------------------------+
| Static Text                |
+----------------------------+
|                            |
|                            |
|                            |
|                            |
| CListBox                   |
|                            |
|                            |
|                            |
|                            |
+----------------------------+

+----------------------------+
| Static Text                |
+----------------------------+
|                            |
|                            |
|                            |
|                            |
| CListBox                   |
|                            |
|                            |
|                            |
|                            |
+----------------------------+
| Static Text                |
+----------------------------+
|                            |
|                            |
|                            |
|                            |
| CListBox                   |
| Static Text here, too!     |
|                            |
|                            |
|                            |
+----------------------------+

__EPCWS_CAPTION_HOVER | __EPCWS_CAPTION_TOOLTIPS | __EPCWS_CAPTION_CENTER_TEXT | 
__EPCWS_SINGLE_EXPANDED | __EPCWS_SINGLE_FULL_SIZE

__EPCWS_CAPTION_HOVER | __EPCWS_CAPTION_TOOLTIPS | __EPCWS_CAPTION_CENTER_TEXT | 
__EPCWS_SINGLE_EXPANDED | __EPCWS_SINGLE_FULL_SIZE | __EPCWS_NOT_ALL_CONTRACTED

Please invoke the CExtPageContainerWnd::Create() method and specify the WS_CHILD|WS_VISIBLE|WS_CLIPCHILDREN|WS_CLIPSIBLINGS flags in its dwWindowStyle parameter. The overlapping effect should be fixed.

Unfortunately, this did not fix the problem...

Originally, I was using the __EPCWS_SINGLE_EXPANDED and __EPCWS_SINGLE_FULL_SIZE style bits. I then decided that I wanted to use __EPCWS_NOT_ALL_CONTRACTED. When I did this, the pages started to animate when clicked on, which is what I don’t want. I then checked the docs for __EPCWS_NO_EXPAND_ANIMATION, and it says that this is the same as (__EPCWS_SINGLE_EXPANDED|__EPCWS_SINGLE_FULL_SIZE|__EPCWS_NOT_ALL_CONTRACTED). However, that isn’t the case, because I use those style bits already, and it’s animating.

Here is the exact style I’m using:

__EPCWS_CAPTION_HOVER | __EPCWS_CAPTION_TOOLTIPS | __EPCWS_CAPTION_CENTER_TEXT | 
__EPCWS_SINGLE_EXPANDED | __EPCWS_SINGLE_FULL_SIZE | __EPCWS_NOT_ALL_CONTRACTED

The __EPCWS_NOT_ALL_CONTRACTED style does nothing if the__EPCWS_SINGLE_FULL_SIZE and __EPCWS_SINGLE_EXPANDED styles are turned on. Please run the PageContainer sample application. The first three check boxes inside the Page Container Options group box correspond to the __EPCWS_SINGLE_EXPANDED, __EPCWS_SINGLE_FULL_SIZE and __EPCWS_NOT_ALL_CONTRACTED styles. If the first and the second are checked, then the third one does not affect the page container’s layout.

I’d like my page container to notify my application when a user expands one of the page dialogs. I tried to override OnPageContainerCaptionPressedStop and simply use the pPageInfo parameter, but that parameter doesn’t necessarily provide the information that I need (which page is expanded). So I went ahead and implemented it as follows:

void MyExtPageContainerWnd::OnPageContainerCaptionPressedStop( CExtPageContainerWnd::PAGE_ITEM_INFO* pPageInfo)
{
	CExtPageContainerWnd::OnPageContainerCaptionPressedStop( pPageInfo);
	TRACE( "%s\n", pPageInfo->TextGet());
	LONG numChevrons = PageGetCount();
	for( LONG i=0; i<numChevrons; i++) {
		CExtPageContainerWnd::PAGE_ITEM_INFO* pInfo = PageGetInfo( i);
		if( !pInfo->IsExpanded())
			continue;
		TRACE( "%s\n", pInfo->TextGet());
	}
}

The CExtPageContainerWnd::OnPageContainerItemExpanded() virtual method is invoked when a page gets expanded/contracted. The CExtPageContainerWnd::OnPageContainerItemExpanding() virtual method is invoked immediately before the page becomes expanded/contracted and returns a flag which indicates whether the page can be expanded/contracted. So, this allows you to fully control the process.

Thanks... can you please add this to the documentation? The v2.40 help file doesn’t have this method listed, and the v2.50 archive doesn’t have a new help file in it.

if I set mode "time" of this type of cell, drop-down button dont’care displayed. And I can choose any date , but i set mode to "only time". It’s a bug?

No, this is not a bug. Just remove the drop-down button:

pCell->ModifyStyle( 0L, __EGCS_BUTTON_DROPDOWN );

Ok, then why no spin button of time inplace control or DOWNUP button in the cell? It’s not right that user must only edit it as text.

From the documentation, I found the following:

CExtGridCell::IconIndexSet(), but it wasn’t clear to me on how it is implemented, or if it is what I need to automatically add an image in my cell. 

Actually, I managed to get it to work, but if someone can let me know if this is the appropriate way, I would appreciate it.  Here are the steps that I took:

In my class derived from CExtPropertyGridCtrl, I provide a test function called:

 void LoadIcons()

{

CExtPropertyGridWnd* pGridWnd = GetActiveGrid();

if (NULL != pGridWnd)

{

HICON hIcon = LoadIcon(NULL, IDI_HAND);

CExtCmdIcon icon(hIcon, true);

pGridWnd->GridIconInsert(&icon);

}

}

then in my subsequent call to populate a grid cell:

I call the function: CExtGridCell::IconIndexSet() with the desired icon that was populated from above

Hi,

I tried to display a  tooltip message (User friendly) message from CView when right click is invoked but it doesn’t show the tooltip message, could you help me ?

void CSampleView::OnRButtonDown(UINT nFlags, CPoint point,BOOL bSelected)
{

 CScrollView::OnRButtonDown(nFlags, point) ;
 CExtPopupMenuTipWnd m_pop;
 m_pop.SetText("test");
 CRect rcAreaScreen ;
 rcAreaScreen.top =100;
 rcAreaScreen.left =100;
 rcAreaScreen.bottom =200;
 rcAreaScreen.right =200;
 this->ClientToScreen( &rcAreaScreen );
 m_pop.Show( this, rcAreaScreen );
 return;

}

or any other method to display the user friendly message

regards

sundar

Hi,

I tried in the same way by declaring

  CExtPopupMenuTipWnd m_pop; in .h file.

But still it doesn’t get displayed. Can you send some piece of code to sundar@cynaptix.com ?

regards

sundar

We’ve just sent you a sample project by e-mail.

Hi,

Is it possible to color the date cells in CExtDurationWnd  (based on some condition) ?

regards

sundar

when I set style of my application CExtPaintManagerOffice2003 or
CExtPaintManagerOffice2005, all profuis controls ( like buttons,comboboxes,...) looks equally (with gradients, hot frames,...), but CExtDurationWnd looks like standard windows checking. So the interface of my application looks not much well

Unfortunately Prof-UIS doesn’t have any class that repaints the spin control. That is why the spin in the duration and date time controls looks like the standard button. Of course, we plan to include such a class into Prof-UIS.

Please take a look at the picture below. The top image has the standard look, which is available now. The bottom image is what we plan to implement. Please let us know whether this is what you mean?

Yes I meaning this. I very waiting your implementation. I hope it will be soon.

Our project comprises an executable, a couple of MFC extension DLL’s and a few regular MFC DLL’s.  All of these modules use Prof-UIS and the MFC extension DLL’s contain Prof-UIS sub-classed objects for use by the other DLL’s and executable.

We have been having an inordinate number of state problems.  Asserts are constantly triggering down in the MFC code due to these state problems.  It is unclear how to integrate Prof-UIS into a project such as ours, there doesn’t seem to be much if any documentation to give us a direction.  We have tried defining __PROF_UIS_FOR_REGULAR_DLL in the non-extension DLL’s.  Is there something that we’re missing?  How can we make Prof-UIS work with our project?

You need to use the RDE version of Prof-UIS in your MFC regular DLL projects (like in ActiveX projects). These projects should have the __PROF_UIS_FOR_REGULAR_DLL preprocessor symbol defined in the project settings. Besides the RDE extension libraries (not only Prof-UIS as RDE) require an explicit initialization invocation from the regular DLL’s code. In case of Prof-UIS, invoke the following code from the InitInstance() virtual method of the CWinApp-derived class in your regular DLL project:

CExt_ProfUIS_ModuleState::InitExtension(
   AfxGetStaticModuleState()
);

CExt_ProfAuto_ModuleState::InitExtension(
   AfxGetStaticModuleState()
);

Ok, I defined __PROF_UIS_FOR_REGULAR_DLL in all of the regular MFC DLL’s and I called CExt_ProfUIS_ModuleState::InitExtension(AfxGetStaticModuleState()); in the InitInstance() of their corrisponding CWinApp objects.  We’re still experiencing a lot of state assertions.  I verified that we are calling AFX_MANAGE_STATE in the first line all of our exported functions.

Is there a problem including Prof-UIS in an MFC Extension DLL that exports objects which are subclassed from Prof-UIS and then using those subclassed objects in other regular MFC DLL’s and Exe’s?  In searching these message boards I found the following quote from a Prof-UIS rep. "You cannot use MFC-extension DLLs (like Prof-UIS) in other DLLs. The DLLs in question should only be used in EXE programs which, in turn, should also be based on MFC."

The customers problem was not exactly like mine and so I’m not sure if this statement applies or not.

Formerly, Prof-UIS could be used in EXE projects only. More than a year ago we added RDE configurations so that the users can use Prof-UIS in ActiveX/regular DLL projects. Besides, the Frame Features ActiveX control is an MFC extension DLL which instantiates lots of classes derived from Prof-UIS implemented in MBCS and UNICODE Prof-UIS RDE DLL modules. We debugged this ActiveX control with different applications and environments without having any assertions. The Frame Features can be used in Internet Explorer, Office VBA forms, Visual Basic 6.0, Visual J++ 6.0, Visual Basic / J# / C++ / C# .NET 2002 / .NET 2003 / 2005. Prof-UIS 2.50 includes a bug fix with tooltip assertions in toolbars, menus and tab window in RDE builds. We do not know any other assertion bugs and may guess the problem with using RDE in your application is hidden somewhere else. What about sending us some project that demonstrates the problems you mentioned so we can find out what’s wrong?