CXTPControlComboBox notification message problems

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

I have a CXTPControlComboBox control used in a RibbonBar.  The only notification that I can get if the user edits the edit control of the combobox is a CBN_EDITCHANGE message.  ON_XTP_EXECUTE does not fire on the edit change (only the listbox change).  The problem is that when the user uses the listbox part of the control, there are actually two CBN_EDITCHANGE messages fired.  I traced this to the function _SetEditText.  When this function is called to insert text into the edit control, if first inserts a NULL entry (causing the message to fire) and then inserts the "real" text causing the second message.

My work around is to test if the GetEditText returns an empty string (the NULL insert) and then ignore that message.  However this forces me to not allow the user to have an empty string as a valid input.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Joe19 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 11 May 2007 Status: Offline Points: 14	Post Options Post Reply Quote Joe19 Report Post Thanks(0) Quote Reply Topic: CXTPControlComboBox notification message problems Posted: 27 May 2007 at 12:44am
	I have a CXTPControlComboBox control used in a RibbonBar. The only notification that I can get if the user edits the edit control of the combobox is a CBN_EDITCHANGE message. ON_XTP_EXECUTE does not fire on the edit change (only the listbox change). The problem is that when the user uses the listbox part of the control, there are actually two CBN_EDITCHANGE messages fired. I traced this to the function _SetEditText. When this function is called to insert text into the edit control, if first inserts a NULL entry (causing the message to fire) and then inserts the "real" text causing the second message. My work around is to test if the GetEditText returns an empty string (the NULL insert) and then ignore that message. However this forces me to not allow the user to have an empty string as a valid input.

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 28 May 2007 at 6:56am
	Thanks, we will add flag to ignore first CBN_EDITCHANGE.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS