DialogBoxIndirect Function

The DialogBoxIndirect macro creates a modal dialog box from a dialog box template in memory. DialogBoxIndirect does not return control until the specified callback function terminates the modal dialog box by calling the EndDialog function. The DialogBoxIndirect macro uses the DialogBoxIndirectParam function.

Syntax

INT_PTR DialogBoxIndirect(      
    HINSTANCE hInstance,     LPCDLGTEMPLATE lpTemplate,     HWND hWndParent,     DLGPROC lpDialogFunc );

Parameters

hInstance
[in] Handle to the module that creates the dialog box.
lpTemplate
[in] Pointer to a global memory object that contains the template that DialogBoxIndirect uses to create the dialog box. A dialog box template consists of a header that describes the dialog box, followed by one or more additional blocks of data that describe each of the controls in the dialog box. The template can use either the standard format or the extended format.

In a standard template for a dialog box, the header is a DLGTEMPLATE structure followed by additional variable-length arrays. The data for each control consists of a DLGITEMTEMPLATE structure followed by additional variable-length arrays.

In an extended template for a dialog box, the header uses the DLGTEMPLATEEX format and the control definitions use the DLGITEMTEMPLATEEX format.

hWndParent
[in] Handle to the window that owns the dialog box.
lpDialogFunc
[in] Pointer to the dialog box procedure. For more information about the dialog box procedure, see DialogProc.

Return Value

If the function succeeds, the return value is the nResult parameter specified in the call to the EndDialog function that was used to terminate the dialog box.

If the function fails because the hWndParent parameter is invalid, the return value is zero. The function returns zero in this case for compatibility with previous versions of Microsoft Windows. If the function fails for any other reason, the return value is –1. To get extended error information, call GetLastError.

Remarks

The DialogBoxIndirect macro uses the CreateWindowEx function to create the dialog box. DialogBoxIndirect then sends a WM_INITDIALOG message to the dialog box procedure. If the template specifies the DS_SETFONT or DS_SHELLFONT style, the function also sends a WM_SETFONT message to the dialog box procedure. The function displays the dialog box (regardless of whether the template specifies the WS_VISIBLE style), disables the owner window, and starts its own message loop to retrieve and dispatch messages for the dialog box.

When the dialog box procedure calls the EndDialog function, DialogBoxIndirect destroys the dialog box, ends the message loop, enables the owner window (if previously enabled), and returns the nResult parameter specified by the dialog box procedure when it called EndDialog.

In a standard dialog box template, the DLGTEMPLATE structure and each of the DLGITEMTEMPLATE structures must be aligned on DWORD boundaries. The creation data array that follows a DLGITEMTEMPLATE structure must also be aligned on a DWORD boundary. All of the other variable-length arrays in the template must be aligned on WORD boundaries.

In an extended dialog box template, the DLGTEMPLATEEX header and each of the DLGITEMTEMPLATEEX control definitions must be aligned on DWORD boundaries. The creation data array, if any, that follows a DLGITEMTEMPLATEEX structure must also be aligned on a DWORD boundary. All of the other variable-length arrays in the template must be aligned on WORD boundaries.

All character strings in the dialog box template, such as titles for the dialog box and buttons, must be Unicode strings. To create code that works on both Windows 95/98/Me and Windows NT/2000/XP, use the MultiByteToWideChar function to generate these Unicode strings.

Windows 95/98/Me: The system can support a maximum of 255 controls per dialog box template. To place more than 255 controls in a dialog box, create the controls in the WM_INITDIALOG message handler rather than placing them in the template.

Example

For an example, see Creating a Template in Memory.

Function Information

Minimum DLL Versionuser32.dll
HeaderDeclared in Winuser.h, include Windows.h
Import libraryUser32.lib
Minimum operating systems Windows 95, Windows NT 3.1
UnicodeImplemented as ANSI and Unicode versions.

See Also

Tags :


Community Content

NianLiu
Does DialogBox call UpdateWindow after ShowWindow?

Let me show the issue,

Use VC++'s wizard to create a skatlon win32 program (GUI), it will have a 'about' dialog box, when you click Help/About... , that dialog box will popup. it is OK after you compile the skatlon program and run it.

Now, I change the code in WndProc from:

--------------------------------------------------

case WM_PAINT:
hdc = BeginPaint(hWnd, &ps);
// TODO: Add any drawing code here...
EndPaint(hWnd, &ps);
break;
---------------------------------------------------

To

---------------------------------------------------

case WM_PAINT:
break;
----------------------------------------------------

That means I will do nothing in WM_PAINT msg, even not pass-though to DefWindowProc. I know this is not recommand by document, but it is reasonable. Now, the issue comes up, after compile and run the program, click Help/About..., the about dialog box doesn't show but the main window is disabled.

I traced the code, it seems like that about dialog box didn't get its first WM_PAINT msg. that means DialogBox function(whatever MACRO) didnot call UpdateWindow after the ShowWindow. Maybe somebody will say: you should validate the main window. Yes, but a model dialog box (about, even MessageBox) should always be displayed no matter the main window re-painted. This really like a bug.

That's it.

Regards,

Nian

Tags : bug dialogbox

Page view tracker