Windows that you have created as user-defined subclasses do not appear on the Object List of your default application, and neither do dialogs. To make them available to end users, you must define a menu line, a button, or another interface element that leads to the window.
To call one of your own windows:
1. | Open the window class (info box or dialog) in the catalog. |
2. | Open the Object Activator in the appropriate context, for example, for a behavior property or as a stand-alone Object Activator for the Yes Action script of a Decision. |
3. | If you have an existing method call script, place the cursor in the Script box at the point in the script where you want to open the new window. |
4. | Drag the window class you want to open from the catalog onto the Script box in the Object Activator. |
| The Object Activator creates a new method call: |
<window class name> [( ? [, ? ...] )].Window.Create()
| Question marks are placeholders for creation arguments in the call. They depend on whether you have defined properties for the window class you are opening. For each user-defined property with an Argument Position in the window, a placeholder appears together with a subnode in the Script tree where you can specify the value(s) to be passed to the opening window. |
| If you have no user-defined properties for the window class you are opening, you also can use the following method call: |
WindowCreate(<window class name>)
5. | If there are placeholders for arguments to be passed to the opening window, for each argument place the cursor on the corresponding subnode in the Script box and provide the argument value by typing a string or referring to object and properties advertised in the Object Activator. |
See Also:
How to Call Your Own Lookup Windows
|