A decision block that allows inspection of the on-screen user interface layout.
If the proceed option is set to Immediately, then UI layout is evaluated for the currently “active” window without pausing the fiber. If set to When UI layout changed, then the fiber will pause until the UI layout has changed and evaluation produced a result.
The XPath expression, if specified, is used to evaluate the UI layout, e.g. to select a particular UI element and/or extract a attribute of it. When passing text as string literal use the xpathEncode function to ensure proper quote character escaping. The “context node” (.) is the entire UI layout document of the “active” window when using proceed Immediately, or the UI element that changed when using proceed When UI layout changed.
The YES path is executed when the evaluated result is a a Number, a String, a Boolean true, a selected Node or a nonempty Node-set. The NO path for a Boolean false, or when using proceed Immediately, not selected a Node or an empty Node-set.
The element “tag” name is the UI element view class. Attribute availability depends on type of UI element and Android version, see table below. Use the Inspect layout button to view the XML layout of a window shown on screen.
| Attribute | Value | Description |
|---|---|---|
@android:checkable | boolean | Can display a check mark |
@android:checked | boolean | Checked state |
@android:choiceMode | text | Choice behavior for collection (Android 5+) |
@android:clickable | boolean | Reacts to clicks |
@android:columnCount | number | Column count of collection (Android 5+) |
@android:contentDescription | text | Associated content description |
@android:contextClickable | boolean | Reacts to context clicks (Android 6+) |
@android:editable | boolean | Has an input method (Android 4.3+) |
@android:enabled | boolean | Allows interaction |
@android:error | text | Error text (Android 5+) |
@android:focusable | boolean | Can take focus |
@android:focused | boolean | Currently has focus |
@android:hint | text | Hint text (Android 8+) |
@android:id | text | Identifier name (Android 4.3+) |
@android:inputType | text | Allowed type of text input, separated by '|' (Android 4.4+) |
@android:labelFor | text | Identifier name of element it’s a label for (Android 4.3+) |
@android:labeledBy | text | Identifier name of label element (Android 4.3+) |
@android:layout_column | number | Column index of collection item (Android 5+) |
@android:layout_columnSpan | number | Column span of collection item (Android 5+) |
@android:layout_height | (number) | Height |
@android:layout_row | number | Row index of collection item (Android 5+) |
@android:layout_rowSpan | number | Row span of collection item (Android 5+) |
@android:layout_width | (number) | Width |
@android:layout_x | (number) | Horizontal position on screen |
@android:layout_y | (number) | Vertical position on screen |
@android:longClickable | boolean | Reacts to long clicks |
@android:max | number | Maximum value for range (Android 5+) |
@android:maxLength | number | Maximum length of text input (Android 5+) |
@android:min | number | Minimum value for range (Android 5+) |
@android:password | boolean | Input characters displayed as password dots |
@android:progress | number | Current value of range (Android 5+) |
@android:rowCount | number | Row count of collection (Android 5+) |
@android:scrollable | boolean | Can scroll |
@android:selected | boolean | Currently selected |
If the floating record window doesn’t generate an event, e.g. when clicking a button, it’s likely due to the UI layout XML changing before its XPath expression can be created. A workaround is to instead use the search feature (magnifying glass icon) to pick the UI element shown on screen, then change the action, e.g. to Click.
On Android 11+ the record interactions and inspect layout windows are hidden on system Settings unless the Allow screen overlays on settings option is enable in system Developer settings.
Note! The XML of a layout can be very large, avoid using result type Node and Node-set that selects entire elements, to then parse and process them using blocks/functions, instead let the XPath do most of the “processing” to limit the result to a Boolean or the value of a specific attribute.