BUG: GetDlgItem() Returns NULL Under Win32s

Last reviewed: June 26, 1997
Article ID: Q149982
The information in this article applies to:
  • The Microsoft Foundation Classes (MFC) included with: - Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1

SYMPTOMS

Calling GetDlgItem() to get the CWnd pointer of a control in a dialog can fail and return NULL under Win32s. DoDataExchange(), which calls DDX functions, also ends up calling GetDlgItem(). This can result in an assert in Dlgdata.cpp, line 43.

CAUSE

This is caused by having extended styles in any of the controls in the dialog. Any extended style converts the dialog resource to a DIALOGEX resource. Win32s does not support DIALOGEX resources. None of the controls in the dialog are be created and the dialog does not display correctly. For details on how to replace the DIALOGEX style, please see the "More Information" section of this article.

RESOLUTION

Remove all extended styles in all the controls in the dialog resource.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching the problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Visual C++ versions 4.2 and later do not support building Win32s applications.

MORE INFORMATION

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q138971
   TITLE     : BUG: Default Dialog-Based Application Doesn't Work in
               Win32s


Additional query words: Dialog based hangs
Keywords : kbprg MfcUI W32s kbbuglist kbprg
Technology : kbMfc
Version : 4.0 4.1
Platform : NT WINDOWS
Issue type : kbbug


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: June 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.