SftTree/DLL 7.5 - Tree Control
SftBox/OCX 5.0 - Combo Box Control
SftButton/OCX 3.0 - Button Control
SftMask/OCX 7.0 - Masked Edit Control
SftTabs/OCX 6.5 - Tab Control (VB6 only)
SftTree/OCX 7.5 - Tree Control
SftPrintPreview/DLL 2.0 - Print Preview Control (discontinued)
SftTree/DLL 7.5 - Tree Control
SftBox/OCX 5.0 - Combo Box Control
SftButton/OCX 3.0 - Button Control
SftDirectory 3.5 - File/Folder Control (discontinued)
SftMask/OCX 7.0 - Masked Edit Control
SftOptions 1.0 - Registry/INI Control (discontinued)
SftPrintPreview/OCX 1.0 - Print Preview Control (discontinued)
SftTabs/OCX 6.5 - Tab Control (VB6 only)
SftTree/OCX 7.5 - Tree Control
SftTabs/NET 6.0 - Tab Control (discontinued)
SftTree/NET 2.0 - Tree Control
Default constructor and destructor for the CSftButton MFC class. CSftButton derives from CWnd and follows MFC's standard window-object lifecycle: an instance is constructed, attached to (or used to create) a HWND, and destroyed.
C++
CSftButton::CSftButton(); CSftButton::~CSftButton();
None.
The constructor takes no arguments and sets no state - the freshly constructed object is not yet attached to a window. Attach it by calling Create, by calling SubclassDlgItem on a button placed in a dialog template, or by casting the result of GetDlgItem.
The destructor calls DestroyWindow if the object is still attached to a HWND; in dialog-based scenarios where the HWND outlives the C++ object (for example a CSftButton temporary obtained from GetDlgItem) this is harmless because the HWND has already been destroyed by the dialog framework.
CSftButton instances created on the heap should be deleted by the application; instances embedded as data members of a dialog or view class are destroyed automatically when the owning class is destroyed.
See Also Create | RegisterApp | Using C++/MFC
