get mouse position

Retrieve the coordinates of the current mouse pointer position.
NameDescriptionTypeModifier
window

(Optional) TA name of the window.

Interface EntityNone
control

(Optional) TA name of the control.

Interface ElementNone
x

(Optional) Variable to receive the current horizontal position of mouse pointer, specified as distance in pixels from left edge of the display element, which may be a control, window or screen (see below).

Default Value: horizontal center of the display element.
StringNone
y

(Optional) Variable to receive the current vertical position of mouse pointer, specified as distance in pixels from top edge of the display element, which may be a control, window or screen (see below).

Default Value: vertical center of the display element.
StringNone
x and y coordinates of the current mouse pointer position.
This action may be used within the following project items: test modules and user-defined actions.
The following settings are applicable to this action: case sensitive, remove double quotes from cells, standard ASCII only, object wait, window wait.
This action is applicable to the following controls: all.
                                
                                    	window	control	x	y
get mouse position	view cars	car select tree	>>left	>>top
                                
                            
  • As a general rule for all actions involving x,y coordinate arguments, the coordinates are specified in pixels relative to the top-left corner of the:
    • control, if the action has window and control arguments, and values are specified for both of them.
    • window, if the action has a value specified for a window argument, but has no control value specified (whether or not the control argument exists).
    • screen, if neither a window nor control value is specified, whether or not such arguments exist.
  • Notes: 
    As for TestArchitect 8.4 Update 2, the coordinates are determined in pixels relative to the top-left corner of the working document.
  • Restriction: 
    This rule should not be taken to imply that any control or window arguments are optional if their associated actions don’t explicitly state that.
  • This action supports the <ignore> modifier. If the string <ignore> is present as the value of any of the arguments, or any argument contains an expression that evaluates to <ignore>, the action is skipped during execution.

Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400