This functionality is supported only if you are using the Classic Agent.
When a control shows up in the
Record Window Declarations dialog box as a
CustomWin, but is actually a standard GUI object which the application developers have renamed, you should map the custom class name to the built-in class name while in the dialog box.
Among the standard classes the
Silk Test Classic displays in the
Class Map dialog box, there are the following three classes that can be described as "meta" classes:
-
BUTTON causes the Agent to treat the object as a kind of button, whether it be an instance of
PushButton,
CheckBox, or
RadioButton. The kind of button depends on the object’s style bits.
-
STATIC causes the Agent to treat the object as Static Text if the appropriate style bits (for example,
SS_LEFT and
SS_CENTER) are set. Otherwise, only the methods of the
AnyWin class apply.
-
MDI client windows are containers that sit between application frame windows and MDI document windows. Mapping a custom object to
MDICLIENT means you do not need a tag for it in order to refer to one of its children. You cannot perform operations on them.