Compatibility Tab

This functionality is supported only if you are using the Classic Agent. For additional information, refer to the Silk Test Classic Classic Agent Help.

The Compatibility tab is available from the Agent Options dialog box. Use the following options only if you are upgrading from a previous release of Silk Test Classic and want to use functionality that matches the previous release.

Don't group radio buttons into a list
If unchecked, treats radio buttons as a group of class RadioList. Otherwise, uses the Release 1.x method of treating radio buttons as individual objects. Default is unchecked.
Use release 1.x version of the class library
If checked, uses QA Partner Release 1 versions of GetChildren, GetClass, and GetParent. Otherwise, uses Release 2 and later versions. Default is unchecked.
Use release 1.x window tags
If checked, generates and operates on tags compatible with Silk Test Classic releases earlier than QA Partner Release 2. Otherwise, uses Release 2 or later tags. Default is unchecked. The Release 2 algorithm affects tags that use index numbers and some tags that use captions. In general, Release 2 tags are more portable, while the earlier algorithm generates more platform-dependent tags. Use this option only if you must run old scripts without any changes.
Don't trim spaces when getting items in controls
If checked, leading and trailing spaces are not trimmed from items on windows. Default is unchecked.
Add ‘Window tags’ to the Record menu
If checked, includes the Record Window Tags menu item on the Record menu. Selecting the Record Window Tags menu item opens the Record Window Tags dialog. Use the Record Window Tags dialog to capture and paste window tags for individual objects into your script or test frame. This dialog is equivalent to the QA Partner Release 1.x Paste Window dialog box, allowing you to paste Release 1.x style window tags into your script. Default is unchecked.
Only use Agent-based clicks (not API-based clicks)
If checked, use API-based clicks when available. An API click is generated internally by the browser, instead of by the agent. API clicks are more reliable than agent clicks, which can click the wrong location of an object. API-based clicks are for browsers only. If cleared, use agent-based clicks even when API-based clicks are available. Default is unchecked.
Use ANSI call

If checked, converts all string parameters (return type, string arguments, strings in record structures that are used as arguments) from W (wide-character, Unicode) to A (ANSI) character format before calling the DLL function internally. Return values and pass-mode variables set to inout that are strings or contain strings within record structures get converted back from A (ANSI) format to W (wide-character) format after calling the DLL. Using this check box makes an ANSI call transparent, as the conversion is done internally. Default is unchecked.

The DLL calling stack does not support return values that are pointers to a record structure. To determine if the function succeeded, use the inout or out pass-mode variable and use the return-type variable as a flag.

Important: If you use DLL functions where you specify string sizes in bytes, remember that W (wide-character) strings are assigned 2 bytes per character, and A (ANSI) strings are assigned 1 byte per character. If you pass a buffer of 1000 characters via an ANSI call, you use 1000 bytes of space, not 2000 bytes. But if you return a string of 1000 characters from a DLL, the W (wide-character) buffer will have 2000 bytes.

4Test statement which sets the selected option

When you set an option, this field displays the 4Test statement that represents the selected option. For example, if you set the Window timeout to 5 seconds on the Timing tab, the following 4Test statement displays:

Agent.SetOption(OPT_WINDOW_TIMEOUT,5)

The statement uses the SetOption method to operate on the agent object. OPT_WINDOW_TIMEOUT is the internal 4Test name of the Window Timeout option and 5 is the current, default value of the option, five seconds.

This code is useful if you want to set a local value for a given agent. You can type or change the code yourself, then click the Copy to Clipboard button to copy the statement to the clipboard.

Copy to Clipboard
Copies the 4Test statement which sets the option to the clipboard.