A tutorial of a tutorial tool... 🤔

1. Automate Community
2. Tutorials & Examples

[Should work on most Android-based devices. May have difficulty scrolling with smaller screens]

This tutorial is about a tool... that makes a tutorial?!? Run the flow to find out more!

This tutorial looks at querying content with SQL, splitting the screen, inspecting layout, and forking with message dialogs. In summation, because the interact block does not work on Automate, we can use inspect layout to obtain screen locations for the Interact touch block.

@global tutorial(communityId or titlePart, steps, returnTo)
/**
@param communityId (int) : Community ID of flow to open. Can be obtained through content query or online link. Alternatively, the function includes it within the first message dialog when run.

@param titlePart (string) : Part of title to select flow. Used only if no community ID is specified -- community ID is recommended due to its constancy.

@param steps (array of arrays) :
Each element should be an array where the first item is the dialog title and the second is the message. It can be followed by regex terms used to identify blocks to select. A trailing wildcard '.*' is automatically added to each term; use '$' to signal an end.
These can be prefixed by a '#:', which specifies how many duplicate matches to skip when reading left to right, top to bottom (defaults to '0:', the first matching block). A '-' in front of the prefix will specify that the function should scroll to the block but not select it.
Instead of regex terms, a single statement number can also be provided to open a statement block for viewing.
*/

This flow was initially inspired by "Block Finder" by Trapier Marshal (#41087)