OFN_EXPLORER from 32-bit Thunk Brings Up Old-Style CommDlg

 Last reviewed: December 11, 1995
Article ID: Q140726
The information in this article applies to:
  • Microsoft Win32 Application Programming Interface (API) included with Microsoft Windows 95

SUMMARY

You can have a 16-bit application running under Windows 95 take advantage of the new Explorer-style FileOpen common dialog by thunking up to a 32-bit DLL, specifying the OFN_EXPLORER style from that DLL, and linking it with the new COMDLG32.DLL. This, however, causes the old-style dialog to come up, instead of the new Explorer-style dialog.

MORE INFORMATION

Although the common dialog function is called from the 32-bit DLL, COMDLG32.DLL detects that the current process is still a 16-bit application and quickly reverts back to the old-style File Open common dialog. This is because the new Explorer-style dialog uses multiple threads, which 16-bit applications do not support.

The only way for a 16-bit application to take advantage of the new Explorer- style functionality is to port to Win32 and make the call to GetOpenFileName() directly.

Additional reference words: 4.00 kbinf
KBCategory: kbprg
KBSubcategory: UsrCmnDlg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 11, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.