|
|
|
Default Button |
SftButton/OCX can be used as a default button as it implements the necessary functionality. Default button handling also depends on the containing application (i.e., your development tool/language). Certain environments may not properly support a default button (see OLEMISC, OLEMISC_ACTSLIKEBUTTON). Particularly property sheets do not always properly support default buttons.
If a button is defined as the default button, the button is painted using a darker outline. If the user presses the Enter key on a form with a default button, the default button's Click event fires.
ActiveX controls are not supported as default buttons.
Visual Basic offers full default button support. The Default property is added to SftButton/OCX by Visual Basic. It defines whether the button is a default button. For more information, please see the Visual Basic documentation.
A SftButton/OCX button control can be defined as the default button using the CDialog::SetDefID function. This function is called at run-time, usually in the OnInitDialog or OnCreate member function of the parent dialog or window.
ActiveX controls are not supported as default buttons.
A SftButton/OCX button control can be defined as the default button
using the Windows dialog manager's DM_SETDEFID message. This message
is sent to the parent dialog, specifying the ID of the default
button, usually while handling the WM_INITDIALOG or WM_CREATE
message of the parent dialog or window.