CONTROL

PLBCMP GUI Only

The CONTROL instruction defines a control object variable. To define a CONTROL object, use the following statement format:

Where:

label

Optional. A Data Label.

target

Optional. A string literal that uniquely identifies an interface for a CONTROL object.

Flags Affected: NONE

Note the following:

1. The CONTROL object is implemented as an ActiveX Control Client interface that allows PL/B to use ActiveX controls.

2. CONTROL objects can be manipulated using the Automation interface.

3. If the CLASS identifier is not provided for the CONTROL variable declaration, it must be supplied during the CREATE operation. If the CLASS identifier is supplied for the CONTROL variable declaration, it cannot be specified for the CREATE operation.

4. The size of the {value} literal is truncated to thirty-nine (39) characters.

5. The properties for a CONTROL object are available as two groups:

• The first group is defined by the normal PL/B property set. These properties are under direct control of the runtime and are defined in the list above.

• The second group of properties is provided only via the Automation interface defined for the CLASS identifier. The user must refer to vendor-supplied documentation for specific properties. The PLBDSIGN browser provides a quick reference to some information.

6. The properties available through the Automation interface use the following syntax:
   *{name}={value}
   or
   @{svar}={value}


Where: 

label

is a string variable containing the property name. Property names are not case sensitive.

value

is a character variable, numeric variable, VARIANT, or AUTOMATION object that is assigned to the property.

7. The PL/B implementation allows event programming. The user should reference the vendor documentation for the ActiveX control object to determine event values. The PLBDSIGN browse capability retrieves quick reference information about an OLE insertable object.

8. When a CONTROL object method is used, the method name identifier is determined by referencing the vendor documentation. The method names are not case sensitive. The method can be specified as a keyword form or as a character variable with a leading '@' character. The acceptable syntax forms are as follows:
   
   {object}.methodname GIVING {result} USING {param}
   or
   {object}.@{svar} GIVING {result} USING {param]

  

9. The {result} is the expected return value for the method. The variable types for {result} can be a string variable, numeric variable, VARIANT object, or AUTOMATION object. Please reference ActiveX control objects vendor documentation for expected return values.

10. The object method parameters identify the expected values required for the {method}. The keyword name of a given {param} can be determined from the ActiveX control object vendor documentation. The {param} keyword names may or may not be used. If the {param} name is not specified, the parameter value must be placed into the {param} list at a valid position as documented for the method. The {param} can have one of the following syntax forms:
    
    {value}
    or
    *{name}={value}
    or
    @{svar}={value}


Where:

value

is a character variable, numeric variable, VARIANT, or AUTOMATION object that is assigned to the property.

name

is the property name. Property names are not case sensitive.

svar

is a string variable containing the property name. Property names are not case sensitive.

 

11. This object is not available when using the PL/B Web Server.

See Also: Object Definitions, Object Output Instructions