CComboBox and OnChar

Posted on 2007-12-05
Last Modified: 2008-03-19
I have defined a class which inherits from CComboBox and have declared the message map for the OnChar method so I can do some processing each time a character is pressed.

The problem is that message doesn't seem to be picked up as the method is never called.
Has anyone any ideas why?

class CMyComboBox : public CComboBox




	CMyComboBox(TItem* item = NULL);

	virtual ~CMyComboBox();


	afx_msg void OnChar(UINT nChar, UINT nRepCnt, UINT nFlags);	


        TItem *m_Item;




CSRAutoCompletionComboBox::CSRAutoCompletionComboBox(TItem* item)

: CComboBox()


	m_Item = item;


/*virtual*/ CSRAutoCompletionComboBox::~CSRAutoCompletionComboBox()



BEGIN_MESSAGE_MAP(CSRAutoCompletionComboBox, CSRComboBox)



void CSRAutoCompletionComboBox::OnChar(UINT nChar, UINT nRepCnt, UINT nFlags)



		CSRComboBox::OnChar(nChar, nRepCnt, nFlags);


Open in new window

Question by:krispin
  • 2
LVL 30

Expert Comment

ID: 20410903
Hi krispin,

probably there's no WM_CHAR message produced from default message processing for a ComboBox for WM_KEYDOWN/WM_KEYUP - you could add a message handler for WM_KEYDOWN instead ...

Hope that helps,

LVL 39

Expert Comment

ID: 20411040
The dialog will catch all key messages. Your overloaded class needs a handler for the WM_GETDLGCODE message, where the dialog asks whether the control wants to handle messages itself:




UINT CMyComboBox::OnGetDlgCode( )

In the class header you need to specify the following member function:

    afx_msg UINT OnGetDlgCode( );

Regards, Alex


Author Comment

ID: 20421058
Thanks for you responses.
Unfortunately neither of these approaches worked.
Like with OnChar(), when a key is pressed, the OnGetDlgCode() method does not get called.

I'm wondering if the message is getting lost somewhere along the way. Let me explain more about what I am trying to do.
I have my combo box as explained, but this is embedded within a List Control (using Report View) which has rows and columns. I have created a class which inherits from List Control so that I can create editable columns (as MFC only provides the ability to edit the first column with the "Edit Lables" property).

So, when a line in the List Control is double clicked, I have a method which checks which column this is, and checks what type of control it should be (at the moment, only Combo Boxes). So, a Combo Box is inserted in the appropriate position.

It is my combo box class that is instantiated and put into position. The idea then that each time I press a key, this combo box will do some sort of processing (for example, if I press tab, the List Control should be notified to remove this combo box from the list). But, as I have stated, the message does not seem to reach the combo box. Is it possible that the message is being sent to the list control instead of the active combo box, or somewhere else for that matter (The List Control is sitting in an MDI child window)?

On a somewhat interesting sidenote;
I tried implementing the PreTranslateMessage method in my combobox class as in my code snippet. When I did this, when I pressed a key, I could do some processing on the key press. So obviously, somewhere after translate and dispatch the message must get sent somewhere else.

This approach will actually work fine for what I need, but I consider this to be a bit messy and would much rather use the message map approach than this. If anyone has any ideas, I'm all ears. Thanks.
BOOL CMyComboBox::PreTranslateMessage(MSG* pMsg)


	if(pMsg->message == WM_KEYDOWN)


		//Do Something



Open in new window

LVL 39

Accepted Solution

itsmeandnobodyelse earned 350 total points
ID: 20421360
>>>> Like with OnChar(), when a key is pressed, the
>>>> OnGetDlgCode() method does not get called.
The OnGetDlgCode will be called only once and the dialog saves the information.

>>>> I have my combo box as explained, but this is embedded
>>>> within a List Control (using Report View) which has rows and columns.
That is the problem, the dialog doesn't know from the combobox cause it was created on the fly or the parent was the reportview control. You would need to put a dummy combobox into the dialog form (make it invisible). Then, let the wizard create a member for the combobox. Change the type of the combobox member from CComboBox to CMyComboBox in the the dialog class header. That way, the combobox was sub-classed with the initial call of the DoDataExchange. 'Subclassing' is a mechanism that makes that messages directed to class CComboBox now were directed to class CMyComboBox. If you do so, the OnGetDlgCode would be called for that combobox member.

>>>> So, a Combo Box is inserted in the appropriate position.
For that case you would move the 'invisible' combobox to the appropriate cell, enable it and show it. You should overwrite the OnKillFocus handler of the combobox so that you can move it back and hide it when it is no more focussed.

You can do similar with an edit control, a button, an image, and more ...

Always have a 'template' which simply was 'activated' and moved to the appropriate cell. Look at the code I posted where I did the same with an edit control.

Regards, Alex

void DynupDlg::OnNMDblClickLstVec(NMHDR *pNMHDR, LRESULT *pResult)


    LPNMLISTVIEW pListView = reinterpret_cast<LPNMLISTVIEW>(pNMHDR);

    int nItems    = m_lstDynRec.GetItemCount();

    int iItem     = pListView->iItem;

    int iSubItem  = pListView->iSubItem;

    // unfortunately pListView doesn't give a valid iItem if clicking on a sub item

    if (iItem >= -1 && iItem < nItems && iSubItem > 0)


        CRect rectGrid;

        // get windows rectangle of the list control


        // unfortunately pListView doesn't give a valid iItem if clicking on a sub item

        if (iItem == -1)


            LVHITTESTINFO lvhti = { 0 };

            // we have to retrieve the 'item' line number 

            // by evaluating the current mouse position 


            // convert to client coordinates

   -= rectGrid.left;


            if (m_lstDynRec.SubItemHitTest(&lvhti ) < 0)

                return;  // ignore clicks outside of grid

            iItem     = lvhti.iItem;

            iSubItem  = lvhti.iSubItem;


        if (iItem < 0    || iItem    > nItems ||

            iSubItem < 1 || iSubItem > 10     ||

            iItem * 10 + iSubItem -1 >= Dynup::s_sizDynRec[m_idxField])


        int col = iSubItem - 1;

        // calculate rectangle for edit cell

        CRect rectDlg;


        rectGrid -= rectDlg.TopLeft();  // relative to left-top of dialog

        CRect rectEdit;

        int off = GetSystemMetrics(SM_CYBORDER);

        int wid = rectGrid.Width() - 2 * off - GetSystemMetrics(SM_CXVSCROLL);

        int wdc = (wid * 94 + 500) / 1000;

        CHeaderCtrl* pHdr = m_lstDynRec.GetHeaderCtrl();

        if (pHdr == 0)


        CRect rectHdr;


        m_lstDynRec.GetItemRect(iItem, rectEdit, LVIR_LABEL);

        int wd1 = rectEdit.Width();

        int hgt = rectEdit.Height();    += - rectHdr.Height() - 2 * off;

        rectEdit.bottom  = + hgt + 2 * off;

        rectEdit.left   += rectGrid.left + wd1 + col * wdc;

        rectEdit.right   = rectEdit.left + wdc;

        CString strDbl = m_lstDynRec.GetItemText(iItem, iSubItem);


        m_gridEdit.SetSel(0, -1);

        m_gridEdit.MoveWindow(rectEdit, TRUE);

        if (!m_gridEdit.IsWindowVisible() || !m_gridEdit.IsWindowEnabled())






        m_gridEdit.m_modified = false;

        m_gridEdit.m_d        = 0.;

        m_gridEdit.m_row      = iItem;

        m_gridEdit.m_col      = iSubItem;

        m_gridEdit.m_pGrid    = &m_lstDynRec;



    *pResult = 1;


Open in new window


Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Unlike C#, C++ doesn't have native support for sealing classes (so they cannot be sub-classed). At the cost of a virtual base class pointer it is possible to implement a pseudo sealing mechanism The trick is to virtually inherit from a base class…
In days of old, returning something by value from a function in C++ was necessarily avoided because it would, invariably, involve one or even two copies of the object being created and potentially costly calls to a copy-constructor and destructor. A…
The viewer will learn how to pass data into a function in C++. This is one step further in using functions. Instead of only printing text onto the console, the function will be able to perform calculations with argumentents given by the user.
The viewer will learn how to user default arguments when defining functions. This method of defining functions will be contrasted with the non-default-argument of defining functions.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now