Thread: DialogBoxIndirect(...) vs. WNDCLASS, CreateWindow etc.

Hello,

I'm just wondering, if you were just after a standard window to use in your program, wouldn't it be quicker and smaller to just:-

Code:

// g_hInstance: global variable for instance handle
// DialogProc:  Dialog window procedure
DWORD *dwDialog;

dwDialog = malloc(24); // Minimum size for a dialog template
DialogBoxIndirect(g_hInstance, dwDialog, NULL, DialogProc);
free(dwDialog);

Than to fill out a WNDCLASS(EX) and call RegisterClass(Ex), CreateWindow(Ex), etc.? You can set the styles in the first two DWORDs (Low and high words), although the window title must be in Unicode in the array, so you might wanna do it in DialogProc's WM_INITDIALOG message, along with sizing the window to your requirements.

Yes, I'm a freak.

Well that would seem quicker but would it be as easy to manage long term?

It's probably easier to have a wrapper for a app window.