Thanks.  It worked out pretty well.  Not having the deleted item resulted in an n squared search, but I'm pretty sure that n will remain small so I should be OK.

--Craig

Hi,

CXTEditListBox seds LBN_XT_DELETEITEM after item deleted using Delete Button, catch it instead:

ON_LBN_XT_DELETEITEM(IDC_EDIT_LIST, OnDeleteItem)

void CEditListPage1::OnDeleteItem()
{
 OnSelchangeEditList();
}

but unfortunally it doesn't send which item was deleted :(... So you must check all items and find deleted one.

The Assert was happening because the listbox had OwnerDraw set to No instead of Variable and HasStrings was set to False instead of True.

Hurray!  I figured out why it is breaking, but I'm not sure how to fix it.  I had put a break point in PreDeleteItem yesterday (at 11:30 pm :-( ) and it was never stopping there.  With your post above, I took another look.

In my dialog box, I have several controls but the two that are involved in this scenario are the CXTCheckListBox and a CXTEditListBox w/ a toolbar.

When an item in the CXTCheckListBox is "checked" it is added to the CXTEditListBox.  When an item in the CXTEditListBox is "deleted" it is unchecked in the CXTCheckListBox .  In order to accomplish this, I captured the WM_DELETE event in my dialog.  This is having two bad side-effects:

1.  It was grabbing the Delete message that the CXTCheckListBox needs, and consequently caused the memory leak.

2.  WM_DELETE is generated not just when an item in the CXTEditListBox is deleted, but also when it is moved up, moved down, or the text is edited.  My capturing of this event was corrupting those actions as well.

How can I capture when an item is deleted from a CXTEditListBox via the Red X on the toolbar without corrupting everything else?

Thanks!
-Craig

Hi,

Strange, I don't see ASSERT in Visual Studio 2003 too... May be you need to recompile library or smth...

Hint to find problem in your sample: try to set brakpoint in

void CXTCheckListBox::PreDeleteItem(LPDELETEITEMSTRUCT lpDeleteItemStruct)

and check if it called.

I build a demo app myself, and cannot reproduce the leak.  I've compared my project to the sample project looking for anything that might cause memory to be handled differently between the two projects and cannot find anything.  Yet...

In my project I am definately seeing a memory leak.  Line 160 in xtchecklistbox.cpp is where the leak is being allocated:

The code you provided fails on ASSERT on line 226 in XTCheckListBox.cpp when it is compiled and run under Visual Studio .NET 2003 and Windows XP SP2.

I'll add my memory checker to your code and check it again.

Can't reproduce it:

2005-12-01_050723_CheckListBoxSample.zip

When I call CXTCheckListBox::SetCheck in my dialog, it causes a memory leak.  Is there a workaround for this?

CXTChecklistbox m_checklistBox;  // in header file

m_checklistBox.Initialize();  // In OnInitInstance

int index = m_checklistBox.AddString("test")  // In OnInitInstance or elsewhere

m_checklistBox.SetCheck(index, TRUE);  // In OnInitInstance or elsewhere

Cancel out of the dialog, exit the application, and if you have a mem leak detector running the mem leak will appear.   I've done extensive testing and this method is definately where the leak is.  Here is the output from mine: