SAMPLE: How to Use Three Different Styles of Property Sheets

Last reviewed: February 15, 1996
Article ID: Q132919
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) versions 3.51, 4.0
  • Microsoft Win32s version 1.30

SUMMARY

The PROPERTY sample code demonstrates how to use three different styles of property sheets: modal, modeless, and wizard.

Download PROPERTY.EXE, a self-extracting file, from the Microsoft Software Library (MSL) on the following services:

  • Microsoft Download Service (MSDL)

          Dial (206) 936-6735 to connect to MSDL
          Download PROPERTY.EXE (size: 22948 bytes) 
    
  • Internet (anonymous FTP)

          ftp ftp.microsoft.com
          Change to the SOFTLIB\MSLFILES directory
          Get PROPERTY.EXE (size: 22948 bytes) 
    

MORE INFORMATION

The main problem in dealing with a modeless property sheet is knowing when to destroy the property sheet. This is handled in the application's main message loop using the PSM_GETCURRENTPAGEHWND message (PropSheet_GetCurrentPageHwnd macro). PSM_GETCURRENTPAGEHWND returns NULL after the OK or Cancel buttons have been clicked (or the dialog box has been closed) and all of the pages have been notified. The application can then call DestroyWindow on the window handle that was returned from the PropertySheet call.

The sample also demonstrates how to use the PropSheetCallback function to modify the property sheet dialog box before or after it is created. The Wizard property sheet is modified to contain a system menu.


Additional reference words: 4.00 1.30 Windows 95
KBCategory: kbprg kbcode kbfile
KBSubcategory:


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: February 15, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.