get column header coordinates

Retrieve the physical position and size of a specified column header of a table.
NameDescriptionTypeModifier
window

TA name of the window.

Interface EntityNone
control

TA name of the table.

Interface ElementNone
column

Column number of the cell. (Column numbers start at 1).

StringNone
left

Variable to receive the returned horizontal position of the left edge of the cell relative to left edge of table (units: pixels).

StringNone
top

Variable to receive the returned vertical position of the top edge of the cell relative to top of table (units: pixels).

StringNone
width

Variable to receive the returned cell width value (units: pixels).

StringNone
height

Variable to receive the returned cell height value (units: pixels).

StringNone
The physical position and size of a specified column header of a table.
This action may be used within the following project items: test modules and user-defined actions.
This action is applicable to the following controls: table, list view, tree table, tree list.
                                
                                    	interface						
use interface	Car Rental						
	&nbsp						
	window	control	column	left	top	width	height
get column header coordinates	view orders	orders table	3	l	t	w	h
                                
                            
  • All returned values are in units of pixels.
  • 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.
  • If the variables in arguments left, top, width and height have not been declared, the action creates them as globals.
  • 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 © 2023 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(800) 322-0333