PRB: Gray Box Appears Using SDK Custom Control in App StudioLast reviewed: August 26, 1997Article ID: Q96760 |
The information in this article applies to:
SYMPTOMSIn the App Studio, or Developer Studio, an attempt to install a "User- Defined" control fails and a gray box appears instead of the visual representation of the control.
CAUSEThe App Studio dialog editor supports the following procedures for "User-Defined" controls:
RESOLUTIONEven though the dialog editor does not display a visual representation of the user-defined control, you can change the size and position of the gray box to reflect the desired placement of the control within the dialog box.
MORE INFORMATIONVisual C++ for Windows (16-bit) supports installing and design-time testing for VBX version 1.0 controls. For 32-bit systems, OLE Controls (OCX) is the preferred custom control architecture. Building and using OLE Controls is fully supported in Visual C++ versions 2.0 and above. See MFC Technical Note 27 included with these versions of Visual C++ for more information. Versions 3.0 and later of the Microsoft Windows Software Development Kit (SDK) define an dynamic-link library (DLL) interface for custom controls. The Dialog Editor provided with the Windows SDK supports installing custom controls and testing their functions. Section 20.2.5 of the Windows SDK "Guide to Programming" manual for version 3.1 documents this interface. Typically, a user-defined control implemented as a DLL registers a WNDCLASS structure in its LibMain() procedure. Once a user-defined control is installed into a dialog box in App Studio, double click on the gray box to change the properties of the control and enter the window class and any style information. Keywords : AppStudioIss Version : 1.0 1.5 1.51 1.52 2.0 2.1 4.0 5.0 Platform : NT WINDOWS Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |