| CloseWindow |
|
Sends a Close command to the active window. | |
| Maximize |
|
Sends a WMaximize command to the active window. | |
| Minimize |
|
Sends a WMinimize command to the active window. | |
| Restore |
|
Sends a RestorePos command to the active window. | |
| SelectMenuItem |
|
Attempts to select a particular text string menuitem. | |
| SelectMenuItemContains |
|
Attempts to select a menuitem based on a partial text match. | |
| SetPosition |
|
Sends a SetPosition command to the window to set the position, size, and status of the window. | |
| VerifyMenuItem |
|
Attempts to verify the state information of a particular text string menuitem. | |
| VerifyMenuItemContains |
|
Attempts to verify the state information of a menuitem found by partial text match. |
| RJ |
This Window command has a problem in that it does not want to use the same recognition methods used by the other Window commands (like SetContext). Particularly, it does not accept the Type=Window portion of these recognition methods. In addition, if the window is a child window of a parent then it expects the ";ChildWindow" add-on in the recognition method. The child may also need the parent as part of its full recognition string like:
ChildWindow=Type=Window;<parent rec>;\;Caption=<caption>;ChildWindow
To handle these child windows, we parse the typical recognition method for our window and attempt to handle these issues. Once SetContext has successfully set our window, we then remove any "Type=Window" substring if present and add the ";ChildWindow" substring if not present.
To take advantage of this, this routine must be called with the child window as a component of the parent window like below:
t, ParentWindow, ChildWindow, CloseWindow
If the routine is called like either of the examples below then default processing will occur. This will merely SetContext on the provided Window and use "CurrentWindow" as the parameter to the command.
t, ParentWindow, ParentWindow, CloseWindow
t, ChildWindow , ChildWindow , CloseWindow (normally won't work)
| RJ |
Sends a WMaximize command to the active window.
This Window command has a problem in that it does not want to use the same recognition methods used by the other Window commands (like SetContext). Particularly, it does not accept the Type=Window portion of these recognition methods. In addition, if the window is a child window of a parent then it expects the ";ChildWindow" add-on in the recognition method. The child may also need the parent as part of its full recognition string like:
ChildWindow=Type=Window;<parent rec>;\;Caption=<caption>;ChildWindow
To handle these child windows, we parse the typical recognition method for our window and attempt to handle these issues. Once SetContext has successfully set our window, we then remove any "Type=Window" substring if present and add the ";ChildWindow" substring if not present.
To take advantage of this, this routine must be called with the child window as a component of the parent window like below:
t, ParentWindow, ChildWindow, Maximize
If the routine is called like either of the examples below then default processing will occur. This will merely SetContext on the provided Window and use "CurrentWindow" as the parameter to the command.
t, ParentWindow, ParentWindow, Maximize
t, ChildWindow , ChildWindow , Maximize (normally won't work)
| RJ |
Sends a WMinimize command to the active window.
This Window command has a problem in that it does not want to use the same recognition methods used by the other Window commands (like SetContext). Particularly, it does not accept the Type=Window portion of these recognition methods. In addition, if the window is a child window of a parent then it expects the ";ChildWindow" add-on in the recognition method. The child may also need the parent as part of its full recognition string like:
ChildWindow=Type=Window;<parent rec>;\;Caption=<caption>;ChildWindow
To handle these child windows, we parse the typical recognition method for our window and attempt to handle these issues. Once SetContext has successfully set our window, we then remove any "Type=Window" substring if present and add the ";ChildWindow" substring if not present.
To take advantage of this, this routine must be called with the child window as a component of the parent window like below:
t, ParentWindow, ChildWindow, Minimize
If the routine is called like either of the examples below then default processing will occur. This will merely SetContext on the provided Window and use "CurrentWindow" as the parameter to the command.
t, ParentWindow, ParentWindow, Minimize
t, ChildWindow , ChildWindow , Minimize (normally won't work)
| RJ |
Sends a RestorePos command to the active window.
This Window command has a problem in that it does not want to use the same recognition methods used by the other Window commands (like SetContext). Particularly, it does not accept the Type=Window portion of these recognition methods. In addition, if the window is a child window of a parent then it expects the ";ChildWindow" add-on in the recognition method. The child may also need the parent as part of its full recognition string like:
ChildWindow=Type=Window;<parent rec>;\;Caption=<caption>;ChildWindow
To handle these child windows, we parse the typical recognition method for our window and attempt to handle these issues. Once SetContext has successfully set our window, we then remove any "Type=Window" substring if present and add the ";ChildWindow" substring if not present.
To take advantage of this, this routine must be called with the child window as a component of the parent window like below:
t, ParentWindow, ChildWindow, Restore
If the routine is called like either of the examples below then default processing will occur. This will merely SetContext on the provided Window and use "CurrentWindow" as the parameter to the command.
t, ParentWindow, ParentWindow, Restore
t, ChildWindow , ChildWindow , Restore (normally won't work)
| RJ |
Attempts to select a particular text string menuitem. The menuitem should be specified in the form "Menu->Menu->MenuItem CTRL+V" with the full text, spaces(if any), and keyboard shortcut text (if any).
Ampersands preceding underlined characters are optional. The routine first verifies that the specified menuitem exists and exits with error if it does not. If it does exist then the selection proceeds using the MenuID retrieved from the found menuitem.
| RJ |
Attempts to select a menuitem based on a partial text match. The menuitem should be specified in the form "Menu->Menu->MenuItem". Each level in the hierarchy can be represented by partial text.
Ampersands preceding underlined characters are optional. The routine first verifies that the specified menuitem exists and exits with error if it does not. If it does exist then the selection proceeds using the MenuID retrieved from the found menuitem.
| RJ |
Sends a SetPosition command to the window to set the position, size, and status of the window. The position, size, and status information is stored in the app map as a subitem in the section for the window. The information should be in the format of:
"0,0,640,480;Status=NORMAL" OR "Coords=0,0,640,480;Status=NORMAL"
That example positions the window at 0,0; sizes it to 640 x 480, and sets it's status to NORMAL. Valid values for STATUS are:
NORMAL, MINIMIZED, and MAXIMIZED
The Window SetPosition command has a problem in that it does not want to use the same recognition methods used by the other Window commands (like SetContext). Particularly, it does not accept the Type=Window portion of these recognition methods. In addition, if the window is a child window of a parent then it expects the ";ChildWindow" add-on in the recognition method. The child may also need the parent as part of its full recognition string like:
ChildWindow=Type=Window;<parent rec>;\;Caption=<caption>;ChildWindow
To handle these child windows, we parse the typical recognition method for our window and attempt to handle these issues. Once SetContext has successfully set our window, we then remove any "Type=Window" substring if present and add the ";ChildWindow" substring if not present.
To take advantage of this, this routine must be called with the child window as a component of the parent window like below:
t, ParentWindow, ChildWindow, SetPosition, ChildPositionReference
If the routine is called like either of the examples below then default processing will occur. This will merely SetContext on the provided Window and use "CurrentWindow" as the parameter to SetPosition.
t, ParentWindow, ParentWindow, SetPosition, ParentPosition
t, ChildWindow , ChildWindow , SetPosition, ChildPosition (normally won't work)
| RJ |
Note 1: This command differs from JavaMenuFunctions.VerifyMenuItemContains as this command seeks a Window object that contains a Window's menu.
Note 2: For RobotJ engine, this command only supports JavaSwing. It may support other clients in the future.
Field 5 : TQ String. the full case-sensitive menu item path to select. Ampersands (&) indicating/preceding underlined characters are optional. The text must include the full text including spaces and any visible shortcut key combinations displayed in the text of the menu item.
Field 6 : QS String. The case-sensitive, space-delimited, double-quote enclosed status information needing verification. Only the state information of interest needs to be specified.
| RJ |
Note 1: This command differs from JavaMenuFunctions.VerifyMenuItemContains as this command seeks a Window object that contains a Window's menu.
Note 2: For RobotJ engine, this command only supports JavaSwing. It may support other clients in the future.
Field 5 : TQ String. the case-sensitive menu item path to select. Ampersands (&) indicating/preceding underlined characters are optional. The text can be any substring of the full text including spaces and any visible shortcut key combinations displayed in the text of the menu item.
Field 6 : QS String. The case-sensitive, space-delimited, double-quote enclosed status information needing verification. Only the state information of interest needs to be specified.