Property Sheets: Creating a Modeless Property Sheet
Normally, the property sheets you create will be modal. When using a modal property sheet, the user must close the property sheet before using any other part of the application. This article describes methods you can use to create a modeless property sheet that allows the user to keep the property sheet open while using other parts of the application.
To display a property sheet as a modeless dialog box instead of as a modal dialog box, call instead of . You must also implement some extra tasks to support a modeless property sheet.
One of the additional tasks is exchanging data between the property sheet and the external object it is modifying when the property sheet is open. This is generally the same task as for standard modeless dialog boxes. Part of this task is implementing a channel of communication between the modeless property sheet and the external object to which the property settings apply. This implementation is far easier if you derive a class from for your modeless property sheet. This article assumes you have done so.
One method for communicating between the modeless property sheet and the external object (the current selection in a view, for example) is to define a pointer from the property sheet to the external object. Define a function (called something like SetMyExternalObject) in the CPropertySheet-derived class to change the pointer whenever the focus changes from one external object to another. The SetMyExternalObject function needs to reset the settings for each property page to reflect the newly selected external object. To accomplish this, the SetMyExternalObject function must be able to access the objects belonging to the CPropertySheet class.
The most convenient way to provide access to property pages within a property sheet is to embed the CPropertyPage objects in the CPropertySheet-derived object. Embedding CPropertyPage objects in the CPropertySheet-derived object differs from the typical design for modal dialog boxes, where the owner of the property sheet creates the CPropertyPage objects and passes them to the property sheet via .
There are many user-interface alternatives for determining when the settings of the modeless property sheet should be applied to an external object. One alternative is to apply the settings of the current property page whenever the user changes any value. Another alternative is to provide an Apply button, which allows the user to accumulate changes in the property pages before committing them to the external object. For information on ways to handle the Apply button, see the article Property Sheets: Handling the Apply Button.
See Also Property Sheets, Property Sheets: Exchanging Data, Life Cycle of a Dialog Box