Windows open file box

[Michael Mattias]

> If you have PBWin9, you can make a DLL that calls DISPLAY ????FILE

For yourself, yes, for sure. But unless I am mistaken or the license has changed, there is some kind of prohibition in the license which says you can't just create a library of "user functions" which are nothing more than callable wrappers for PB intrinsic functions.

Darned if I know how you'd determine if your function is "different enough," though. Maybe it's like pornography: can't define it, but know it when you see it.

[Roger Garstang]

If you have PBWin9, you can make a DLL that calls DISPLAY ????FILE. Your PBCC projects can use it.

Why make a DLL that calls the PB Wrapper that calls the WinAPI from PBCC when you could just call the API straight from the PBCC side and only one EXE file?

[Michael Mattias]

The COMDLG32.INC file included with PB/CC 5.0.1 includes PB-created "OpenFileDialog" and "SaveFileDialog" functions, if you can sacrifice some flexibility in exchange for not having to work directly with the Windows' API.

MCM

[Erich Schulman]

If you have PBWin9, you can make a DLL that calls DISPLAY ????FILE. Your PBCC projects can use it.

[Michael Mattias]

Win API (Common Dialogs): "GetOpenFileName", "GetSaveFileName"

PB/Windows 9+ : "DISPLAY OPENFILE", "DISPLAY SAVEFILE"

PB/CC: Use WinApi.

[Charles Perry]

I remember using an API call or ? which opens a windows dialog box to select a file and navigate the director structure. I can't find it now nor the program where I used it. Anyone know what it is?

Thanks