This functionality is supported only if you are using the Classic Agent.
Silk Test Classic might recognize ActiveX controls, which often have a native class beginning with OLE, as having the native class
ATL:<variable hex #>, or
Silk Test Classic might recognize the ActiveX controls as children of an
ATL:<variable hex #> control. In other cases, the parent control of an ActiveX control might seem to disappear on occasion. In such a case, the following settings in the
extend.ini and
axext.ini files might help.
- If the inconsistent recognition problem involves ATL controls, then first try setting
DontIgnore=ATL in the
[VBOptions] section.
- If the recognition problem occurs when
Silk Test Classic invokes the application under test (AUT) especially if the AUT seems slow to render completely, then try to kill the agent while leaving the application running, and then restart the agent. If
Silk Test Classic recognizes the control properly, then you should be able to correct the problem without having to kill the agent by setting
AxextDelay=<n> in the
[VBOptions] section, where
<n> is the number of seconds that the application should require to start up completely.
Note: The amount of time that
Silk Test Classic requires to recognize the application when it is invoked is extended by
AxextDelay seconds, so you should not make the number too large. In addition, if the application contains frame classes such as
AfxFrameOrView42 or
AfxMDIFrame42, then you should try class-mapping them to
Ignore. Ignoring those windows may eliminate some unnecessary layers and also make the
Silk Test Classic recognition of the window hierarchy more consistent.