This functionality is supported only if you are using the Classic Agent.
You can use 4Test to filter out unnecessary classes, such as invisible containers. Ignoring these unnecessary classes simplifies the object hierarchy and shortens the length of the lines of code in your test scripts and functions. Container classes or ‘frames’ are common in GUI development, but might not be necessary for testing.
You enable Silk Test Classic to ignore instances of a container class through the Class Map dialog box. When you enable Silk Test Classic to ignore these classes, the classes are not recorded.
You can suppress the controls for certain classes for .NET, Java SWT, and Windows API-based applications. Other extensions do not support this type of class-mapping for window classes, so you must modify the extension .ini file in order to ignore window classes in the Java or ActiveX/VB extensions.
After filtering out a custom container class, you may lose the ability to see its child objects.
You can also map a class to LookUnder to look ‘through’ the class, seeing the objects under it. For example, there is a BlackFrame class in Visual Basic that is a 3-D black border around controls. LookUnder is not in the standard classes list, so if you want to use it you must type it in.