Load an ActiveX control into a container
|
WTSupported in traditional Synergy on Windows
|
|
|
|
control_id = %AX_LOAD(container_id, control_name, [xpos], [ypos], [xsize], [ysize], [license] & [, autobind_prefix])
Return value
control_id
The positive, nonzero ID of the loaded ActiveX control. (D_HANDLE)
Arguments
container_id
The ActiveX container ID returned by an %AX_CREATE call. (D_HANDLE)
control_name
A string that contains the identifying name of the ActiveX control. (a)
xpos
(optional) The X pixel position within the container of the upper-left corner of the ActiveX control. (n)
ypos
(optional) The Y pixel position within the container of the upper-left corner of the ActiveX control. (n)
xsize
(optional) The pixel width of the ActiveX control. (n)
ysize
(optional) The pixel height of the ActiveX control. (n)
license
(optional) The license string required to run the ActiveX control at an unlicensed site. (a)
autobind_prefix
(optional) A routine prefix that causes automatic binding to occur. If this argument is present, each event is automatically bound to any existing routine whose name is the specified prefix followed by the event’s name. (a)
Discussion
The default value for xpos and ypos is zero, which positions the ActiveX control at the upper-left corner of the container. If xsize or ysize is not specified, the default is the respective edge of the container’s display area. (The display area is the total area of the container minus all borders, headers, and so forth.)
The control_name and license strings can be determined using the ActiveX Diagnostic utility. See Testing an ActiveX control for more information.
Specifying the autobind_prefix argument eliminates the need to manually bind each callback subroutine using AX_BIND.
Examples
See Sample program.
