Example - Case 1: Using a text value for node path

        
        	window	tree	node path	menu item	variable	x	y
get tree node menu state	sample	tree view	Item.0/Item.1	Item.1->Item.1.1	state		
        
    

Result

Example - Case 2: Using a numerical index for node path

        
        	window	tree	node path	menu item	variable	x	y
get tree node menu state	sample	tree view	1/1	Item.1->Item.1.1	state		
        
    

Result

• node path argument:
  • The node path may be specified by its display textor by a numerical index representing its cardinal placement in its branch, with index values starting at 1.
  • If a node path of more than one item must be specified, use forward slashes ( / ) as delimiters between node levels.
• menu item argument:
  • If a menu path of more than one item must be specified, use arrow symbols ( -> ) as delimiters between menu items. For example, Vehicles->Cars->Four-door sedans.
• Enclose a numerical text string in quotation marks to differentiate it from a numerical index value. For example, if a text value of an item in a control has a value of 12, you should reference that item by passing 12 surrounded by quotation marks (that is, "12") instead of the numerical 12. Passing the numerical 12 is treated as a reference to an item with an index of 12, rather than an item holding a text string value of 12.
• variable argument:
  • If the variable in argument variable has not been declared, the action creates it as a global.
  • If the variable argument is left empty, TestArchitect supplies a global variable with the name _result.
• 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.