Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

                                                 ◄Contents►  ◄Index►  ◄Back►
──────────────────────────────────────────────────────────────────────────────
 Custom Control
 
 ■ Custom controls extend the set of standard controls available in Visual
   Basic for MS-DOS. You access this custom-control functionality in Visual
   Basic via custom-control libraries (.LIB) and Quick libraries (.QLB).
 
 ■ Like standard controls, custom controls recognize a predefined set of
   properties, events, and methods. For more information on the specific
   features and functionality of a custom control, refer to the
   documentation that came with the control.
 
 ■ For more information on using custom controls, see Chapter 19 in the
   "Programmer's Guide."
 
 ■ For more information on creating custom controls, see Chapter 1 of
   "Professional Features" (Professional Edition only).
 
 ■ Only one Quick library can be loaded at a time. Therefore, to use more
   than one custom control within your application, the custom-control Quick
   libraries must be combined. Use the LINK utility to combine Quick
   libraries. See: ◄Quick Libraries►  ◄LINK Command-Line Options►
 
 ■ When a custom control Quick library is loaded with Visual Basic, the
   control(s) defined within that Quick library appear in the Toolbox and
   on the Tools menu within the Form Designer.
 
 ■ At design time, custom controls appear as picture box controls with
   the control name displayed inside the control.
 
                             ┌───────────┐
                             │ Custom1   │
                             │           │
                             │           │
                             └───────────┘
 
 ■ The actual "look" of a custom control as defined by the custom-control
   developer is not available until run time.
 
 ■ At design time, property settings other than Left, Top, Width, Height,
   and BorderStyle have no visible effects. In addition, no control-specific
   range checking is done for property values that you specify. Be sure to
   verify that your custom-control property settings will be valid at run
   time by referring to the specific custom control documentation.
 
 See: ◄Controls Summary►