Click here to Skip to main content
Click here to Skip to main content

Tagged as

Using text callbacks in ListView Controls

, 26 Nov 1999 CPOL
Rate this:
Please Sign up or sign in to vote.
Shows how to use text callbacks in list controls
  • Download files - 16 Kb

    If you store you application data and you wish to save some time and memory, you can have the list ask your application for the strings to display in the list on the fly, instead of having the list store the strings explicitly. This will reduce the amount of memory your final app needs and will make filling and deleting the list contents quicker, at the expense of slightly slower display time. (If you are displaying several thousand items in the list, the time saved in filling and cleaning the list more than makes up for fractionally slower display). Furthermore, list sorting can become lightning fast.

    Suppose your data is stored in your app in structures "ItemStruct" declared:

    typedef struct {
    	int nItemNo;
    	CString strName;
    } ItemStruct;
    

    and each structure is stored in an array, list or map. The easiest way to let the list know about each item is to store a pointer to each item in the lParam field of the LV_ITEM structure you pass to the CListCtrl::InsertItem function.

    Firstly, when you add a new item to the list you should set the LVIF_PARAM bit in the mask field of your LV_ITEM structure that you are using. This lets the list know that the lParam field of your LV_ITEM contains data.

    You may want to create a helper function to add a new item to the list like:

    BOOL CMyListCtrl::AddItem(ItemStruct* pItem, int nPos /* = -1 */)
    {
    	int nNumItems = GetItemCount();
    	int nInsertPos = (nPos >= 0 && nPos <= nNumItems)? nPos : nNumItems;
    
    	LV_ITEM Item;
    	Item.lParam	  = (LPARAM) pItem;		// Store the pointer to the data
    	Item.pszText  = LPSTR_TEXTCALLBACK;		// using callbacks to get the text
    	Item.mask	  = LVIF_TEXT | LVIF_PARAM;	// lParam and pszText fields active
    	Item.iItem	  = nInsertPos;			// position to insert new item
    	Item.iSubItem = 0;
    	
    	if (InsertItem(&Item) < 0) 
    		return FALSE;					
    	else
    		return TRUE;
    }
    

    The LPSTR_TEXTCALLBACK value for the pszText field tells the list that it should use callbacks to get the text to display, instead of storing the text itself. Every time the list needs to display text, it sends a LVN_GETDISPINFO. We don't add text for the subitems, since they will be dealt with in the LVN_GETDISPINFO handler as well.

    You need to handle the windows notification LVN_GETDISPINFO using the following:

    BEGIN_MESSAGE_MAP(CMyListCtrl, CListCtrl)
    	//{{AFX_MSG_MAP(CMyListCtrl)
    	ON_NOTIFY_REFLECT(LVN_GETDISPINFO, OnGetDispInfo)
    	//}}AFX_MSG_MAP
    END_MESSAGE_MAP()
    

    and have an accompanying function declared in you class definition:

    class CMyListCtrl 
    {
    // .. other declarations
    
    // Generated message map functions
    protected:
    	//{{AFX_MSG(CMyListCtrl)
    	afx_msg void OnGetDispInfo(NMHDR* pNMHDR, LRESULT* pResult);
    	//}}AFX_MSG
    };
    

    The handler function should look something like:

    void CMyListCtrl::OnGetDispInfo(NMHDR* pNMHDR, LRESULT* pResult) 
    {
    	LV_DISPINFO* pDispInfo = (LV_DISPINFO*)pNMHDR;
    
    	if (pDispInfo->item.mask & LVIF_TEXT)
    	{
    		ItemStruct* pAppItem = (ItemStruct*) pDispInfo->item.lParam;
    		CString strField = QueryItemText(pDispInfo->item.iItem, 
    							   pDispInfo->item.iSubItem);
    		LPTSTR pstrBuffer = AddPool(&strField);	
    
    		pDispInfo->item.pszText = pstrBuffer;
    	}	
    	*pResult = 0;
    }
    

    The NMHDR variable contains the list view display info, which in turn holds a LV_ITEM member specifying the item and subitem it's after, and what sort of info it's after. In our case we are only specifying text, so we only deal with notifications where the pDispInfo->item.mask equals LVIF_TEXT. We get a pointer to our Apps data through the lParam field of LV_ITEM, and from this we get a text representation of our data (I'm using another helper function "QueryItemText" implemented as

    // returns a CString representation for the data in row nRow, column nCol
    CString CMyListCtrl::QueryItemText(int nRow, int nCol)
    {
    	CString strField;
    	ItemStruct* pAppItem = (ItemStruct*) GetItemData(nRow);
    	if (!pAppItem) return strField;
    
    	switch (nCol) {
    		case 0:	strField.Format("%d",pAppItem->nItemNo);	break;
    		case 1: strField = pAppItem->strName;			break;
    		default: ASSERT(FALSE);
    	}
    
    	return strField;
    }
    

    The main reason I use the "QuesryItemText" function is that since we are now using text callbacks, functions like CListCtrl::GetItemText no longer work. If you use GetItemText (for instance in TitleTips or InPlaceEdit's) then you must replace them with QueryItemText in order for them to work. The two lines:

    	LPTSTR pstrBuffer = AddPool(&strField);	
    	pDispInfo->item.pszText = pstrBuffer;
    

    in the OnGetDispInfo function were taken from Mike Blaszczak's program "ApiBrow" (get it either online or from his book "Proffessional MFC with Visual C++ 5"). It handles the bizarre situtation that the list control requires the buffer you pass back from the OnGetDispInfo to be valid for 2 more LVN_GETDISPINFO notifications. His solution was a simple caching to store sufficient copies so the list control doesn't have a cow. It goes something like this:

    LPTSTR CMyListCtrl::AddPool(CString* pstr)
    {
    	LPTSTR pstrRetVal;
    	int nOldest = m_nNextFree;
    
    	m_strCPool[m_nNextFree] = *pstr;
    	pstrRetVal = m_strCPool[m_nNextFree].LockBuffer();
    	m_pstrPool[m_nNextFree++] = pstrRetVal;
    	m_strCPool[nOldest].ReleaseBuffer();
    
    	if (m_nNextFree == 3)
    		m_nNextFree = 0;
    	return pstrRetVal;
    }
    

    You will need to declare the protected attributes

    	CString m_strCPool[3];
    	LPTSTR  m_pstrPool[3];
    	int     m_nNextFree;
    

    in your class definition.

    And that's all there is to it!

    One advantage of storing the data in the lParam field is that sorting become very quick. A column sort function as already been provided in in the MFC programmers sourcebook. It is prototyped:

    BOOL CMasterListCtrl::SortTextItems(int nCol, BOOL bAscending, 
    					int low /*= 0*/, int high /*= -1*/ );
    

    I will ignore the high and low parameters (sorry!) and instead implement a different version: (see the docs on CListCtrl::SortItems for details)

    typedef struct {
    	int nColumn;
    	BOOL bAscending;
    } SORTINFO;
    
    BOOL CMasterListCtrl::SortTextItems(int nCol, BOOL bAscending)
    {
    	CWaitCursor waiter;
    
    	SORTINFO si;
    	si.nColumn = m_nSortColumn;
    	si.bAscending = m_bSortAscending;
    	return SortItems(CompareFunc, (LPARAM) &si);
    }
    
    int CALLBACK CompareFunc(LPARAM lParam1, LPARAM lParam2, LPARAM lParamSort)
    {
    	ItemStruct *pItem1 = (ItemStruct*) lParam1;
    	ItemStruct *pItem2 = (ItemStruct*) lParam2;
    	SORTINFO* pSortInfo = (SORTINFO*) lParamSort;
    	ASSERT(pItem1 && pItem2 && pSortInfo);
    
    	int result;
    	switch (pSortInfo->nColumn)
    	{
    		case 0: 
    		  if (pItem1->nItemNo < pItem2->nItemNo) 
    			result = -1;
    		  else if (pItem1->nItemNo == pItem2->nItemNo) 
    			result = 0;
    		  else 
    			result = 1;
    		  break;
    
    		case 1: 
    		  result = pItem1->strName.Compare(pItem2->strName); 
    		  break;
    
    		default:
    		  ASSERT(FALSE);
    	}
    
    	if (!pSortInfo->bAscending) 
    	  result = -result;
    
    	return result;
    }
    
  • License

    This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

    Share

    About the Author

    Chris Maunder
    Founder CodeProject
    Canada Canada
    Chris is the Co-founder, Administrator, Architect, Chief Editor and Shameless Hack who wrote and runs The Code Project. He's been programming since 1988 while pretending to be, in various guises, an astrophysicist, mathematician, physicist, hydrologist, geomorphologist, defence intelligence researcher and then, when all that got a bit rough on the nerves, a web developer. He is a Microsoft Visual C++ MVP both globally and for Canada locally.
     
    His programming experience includes C/C++, C#, SQL, MFC, ASP, ASP.NET, and far, far too much FORTRAN. He has worked on PocketPCs, AIX mainframes, Sun workstations, and a CRAY YMP C90 behemoth but finds notebooks take up less desk space.
     
    He dodges, he weaves, and he never gets enough sleep. He is kind to small animals.
     
    Chris was born and bred in Australia but splits his time between Toronto and Melbourne, depending on the weather. For relaxation he is into road cycling, snowboarding, rock climbing, and storm chasing.
    Follow on   Twitter   Google+   LinkedIn

    Comments and Discussions

     
    GeneralI can't get this to work in a Windows Explorer architecture project... PinmemberBen Aldhouse24-Jun-09 12:10 
    GeneralUpdating the object data PinmemberJohn Andzelik3-Sep-08 11:02 
    QuestionHow do Listview controls store data internally? PinsussSlimso13-Apr-05 12:10 
    GeneralFlickering if using more than 300 items PinmemberBenj1028-Dec-04 5:28 
    GeneralTime to set &quot;LPSTR_TEXTCALLBACK&quot; Pinmemberv_fsr5-Dec-03 10:32 
    GeneralItem Rect PinmemberBrad Bruce20-Oct-03 9:52 
    GeneralHELP! PLEASE! Dialog &amp; List Control Data Exchange PinmemberCharlieC20-Aug-03 10:39 
    GeneralHELP!! Pinmembersimonzb7-Aug-03 22:02 
    GeneralUpdating LV_ITEM doesn't update in list view display. PinsussWilliam Welbes1-May-03 12:05 
    GeneralRe: Updating LV_ITEM doesn't update in list view display. PinmemberBhawnaA2-Jul-07 21:53 
    GeneralSpeed issue when deleting items. PinmemberDavid Fleming17-Mar-03 22:27 
    GeneralRe: Speed issue when deleting items. PinmemberDavid Fleming19-Mar-03 14:01 
    GeneralText in a ListView PinmemberPeterlip27-Feb-03 14:22 
    GeneralRe: Text in a ListView PinmemberPeterlip27-Feb-03 14:33 
    QuestionHow to break the 260 bytes limitations ? PinmemberKarl14-Jun-02 5:36 
    AnswerRe: How to break the 260 bytes limitations ? Pinsussdeey26-Aug-02 16:38 
    GeneralRe: How to break the 260 bytes limitations ? PinmemberKarl26-Aug-02 22:25 
    AnswerRe: How to break the 260 bytes limitations ? PinsussWicket_13-Feb-03 22:57 
    GeneralRe: How to break the 260 bytes limitations ? PinmemberMke5-Mar-03 8:19 
    GeneralRe: How to break the 260 bytes limitations ? PinmemberPhilnessosity8-Apr-03 18:10 
    AnswerRe: How to break the 260 bytes limitations ? PinmemberTom Archer8-Aug-04 5:28 
    GeneralRe: How to break the 260 bytes limitations ? PinmemberKaЯl8-Aug-04 6:11 
    GeneralProblem at AddItem() function PinmemberEhud5-Jun-02 21:10 
    GeneralRe: Problem at AddItem() function PinmemberEhud5-Jun-02 22:22 
    GeneralDon't forget to initialize m_nNextFree in the constructor PinmemberTrevor Ash11-Jan-02 19:03 
    GeneralSpeed and Memory usage question. PinmemberDavid Fleming19-Nov-01 12:26 
    GeneralWM_PAINT message PinmemberDavid Fleming19-Nov-01 12:12 
    GeneralSorting not in download code PinmemberAllan McCombs12-Dec-00 16:21 
    GeneralRe: Sorting not in download code PinmemberChandranath21-Nov-01 21:20 
    Generallistview font Pinsussmeir12-Oct-00 4:52 
    GeneralRe: listview font PinmemberDavid Fleming19-Nov-01 21:02 
    GeneralUsing text callbacks in Listview controls PinsussBen Nguyen23-Aug-00 5:36 
    GeneralUsing AddPool Pinsussherb illfelder26-May-00 6:22 
    GeneralRe: Using AddPool (Memory leak?) PinmemberJian Ruan25-Nov-02 20:26 
    GeneralRe: Using AddPool (Memory leak?) PinmemberHerbert Illfelder26-Nov-02 4:33 

    General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

    Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

    | Advertise | Privacy | Terms of Use | Mobile
    Web03 | 2.8.141220.1 | Last Updated 27 Nov 1999
    Article Copyright 1999 by Chris Maunder
    Everything else Copyright © CodeProject, 1999-2014
    Layout: fixed | fluid