🚀 go-pugleaf

gb8@prism.gatech.EDU (BEEBE,GARY E) writes:


>The FILEDLG member assignment that causes the error is
>
>         Dlgdat.pfnDlgProc=NULL;

>where FILEDLG Dlgdat; was previously declared. This assignemnt was recommended
>in the RED BOOK's (although I have my reservations as to its neccesity).

Double-check the header file (I think it is PMCTLS.H) to be sure that the name
is correct as you typed it.  Sometimes there are typos in the documentation.

>The question is: If you declare the pointer to the dialog procedure
>to be NULL, how does the WinFileDlg call know where to process the default
>dialog controls? Can someone recommend a validated source of accurate information describing the use of the WinFileDlg function?

This is NOT the real dialog proc.  The dialog proc pointed to by that parameter
is a SUBCLASS PROC.  Basically, if you put a dialog proc of your own there,
the standard File dialog will be created and then the system will immediately
call WinSubclassWindow() with your proc and the file dialog as window.  It is
your responsibility in your subclass proc to call WinDefFileDlgProc() or
whatever the default proc is called.
______________________________________________________________________________
     Michael Harris - harris@catt.ncsu.edu or harris@carvm3.vnet.ibm.com
 System Administrator, Computer & Technologies Theme Program, NC State Univ.
(My opinions are my own and do not represent those of NCSU or IBM Corporation)