This functionality is supported only if you are using the Classic Agent.
Consider the Direction control in the Find dialog box of the Text Editor application, which allows a user to specify the direction (up or down) of searches. Suppose that this control is implemented as a check box on one GUI, but as a radio list on all other GUIs. As a radio list, the user clicks either the Up or the Down option button. As a check box, the user checks the check box to select Up, and leaves the check box unchecked to select Down.
The first step in solving this portability scenario is to create a new window class that you will use for the object on all platforms. The class you need to define, in effect, generalizes several distinct 4Test classes into one logical class.
To achieve this generalization, you:
Here is the class declaration, which is arbitrarily named DirButton:
// The class is derived from Control winclass DirButton : Control tag "[RadioList]" msw9x tag "[CheckBox]" void Select (LISTITEM Item optional) BOOLEAN bState switch (GetGUIType ()) case msw9x bState = (Item == "Up") CheckBox (WndTag).SetState (bState) default RadioList (WndTag).Select (Item)
The next step is to change your window declarations so that the control has the new class.
Continuing the example, you change the class of the control named Direction to DirButton.
window DialogBox Find tag "Find" parent TextEditor DirButton Direction tag "Direction"