Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

BuildDisplayTable

Creates a display table from the property page data contained in one or more DTPAGE structures.

Header file:

Mapiutil.h

Implemented by:

MAPI

Called by:

Service providers

STDAPI BuildDisplayTable(
  LPALLOCATEBUFFER lpAllocateBuffer,
  LPALLOCATEMORE lpAllocateMore,
  LPFREEBUFFER lpFreeBuffer,
  LPMALLOC lpMalloc,
  HINSTANCE hInstance,
  UINT cPages,
  LPDTPAGE lpPage,
  ULONG ulFlags,
  LPMAPITABLE * lppTable,
  LPTABLEDATA * lppTblData
);

Parameters

lpAllocateBuffer

[in] Pointer to the MAPIAllocateBuffer function, to be used to allocate memory.

lpAllocateMore

[in] Pointer to the MAPIAllocateMore function, to be used to allocate additional memory.

lpFreeBuffer

[in] Pointer to the MAPIFreeBuffer function, to be used to free memory.

lpMalloc

Unused; should be set to NULL.

hInstance

[in] An instance of a MAPI object from which BuildDisplayTable retrieves resources.

cPages

[in] Count of DTPAGE structures in the array pointed to by the lpPage parameter.

lpPage

[in] Pointer to an array of DTPAGE structures that contain information about the display table pages to be built.

ulFlags

[in] Bitmask of flags. The following flag can be set:

MAPI_UNICODE

The passed-in strings are in Unicode format. If the MAPI_UNICODE flag is not set, the strings are in ANSI format.

lppTable

[out] Pointer to a pointer to the display table, which exposes the IMAPITable interface.

lppTblData

[in, out] Pointer to a pointer to a table data object exposing the ITableData interface on the table returned in the lppTable parameter. If no table data object is desired, lppTblData should be set to NULL instead of a pointer value.

MAPI uses the functions pointed to by lpAllocateBuffer, lpAllocateMore, and lpFreeBuffer for most memory allocation and deallocation, in particular to allocate memory for use by client applications when calling object interfaces such as IMAPIProp::GetProps and IMAPITable::QueryRows.

Everything possible is read from the dialog resource, including:

  • The page title that is, the ulbLpszLabel member of the DTBLPAGE structure read from the dialog title in the resource.

  • All control titles that is, the ulbLpszLabel members of other control structures read from the control text in the resource.

   BuildDisplayTable overwrites anything passed in the input control structures with information from the dialog resource, which means the caller of BuildDisplayTable cannot dynamically specify page or control titles. Callers who need to do that can have BuildDisplayTable return the table data object in lppTableData and change rows in it; or they can build the display table by hand in a table data object instead.

If lppTableData is not set to NULL, the provider is responsible for freeing the table data object when it is finished with the display table.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.