home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!swrinde!gatech!prism!gb8
- From: gb8@prism.gatech.EDU (BEEBE)
- Newsgroups: comp.os.os2.programmer
- Subject: Help with the WinFileDlg function
- Message-ID: <74677@hydra.gatech.EDU>
- Date: 13 Nov 92 11:34:08 GMT
- Organization: Georgia Institute of Technology
- Lines: 33
-
-
-
- Hello All,
-
- I've run into a bit of a snafu on the proper utilization of the WinFileDlg
- API function. The documentation in the RED BOOK's appears to be hopelessly
- incorrect. I used the code they suggested to initialize the FILEDLG struc-
- ture and ended up with about 10 "identifier must be a member of the structure
- or union class" errors and one "severe error: general compiler fault" or
- some such thing. I've check the online help and fixed most of the declaritory
- errors but the "severe error" persists. 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). The
- general idea is to use a default "OPEN FILE" dialog box to return a HFILE
- pointer. 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?
-
- Thank in Advance,
- Gary
-
-
-
-
- --
- BEEBE,GARY E
- Georgia Institute of Technology, Atlanta Georgia, 30332
- uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gb8
- Internet: gb8@prism.gatech.edu
-